[feelamee]

why use modules if PCH on your diagram is not much worse in compile times?

[nickelpro]

Macro hygiene, static initialization ordering, control over symbol export (no more detail namespaces), slightly higher ceiling for compile-time and optimization performance.

If these aren't compelling, there's no real reason.

[feelamee]

We live with that for *decades*. For me this is not a daily problem. So yes, this is not compelling, unfortunately.

[WalterBright]

Having implemented PCH for C and C++, it is an uuugly hack, which is why D has modules instead.

[bluGill]

modules are the future and the rules for are well thought out. Ever compiler has their own version of PCH and they all work different in annoying ways.

[Maxatar]

Modules are the future... and will always be the future.

[feelamee]

> Ever compiler has their own version of PCH and they all work different in annoying ways.

I don't care because I use cmake