Comment by pjmlp
6 days ago
> C++ is actually very fast to compile, the slowdowns come mostly from the way the standard library is implemented.
Only if using classical headers, std as module is already a reality on VC++.
6 days ago
> C++ is actually very fast to compile, the slowdowns come mostly from the way the standard library is implemented.
Only if using classical headers, std as module is already a reality on VC++.
wasn't there a lot of talk that modules are still not really working, in practice I mean?
Depends on where you are.
VC++ and clang latest with MSBuild or CMake/ninja are there, minus some bugs or code completion misbehaving (but bearable).
GCC 16 is mostly ok now, also with CMake/ninja.
All my hobby coding in C++ makes use of modules, at work it is a different matter, where libraries to be consumed by Java/.NET/nodejs, are still using C++17 as baseline.
You can easily check, https://github.com/pjmlp/RaytracingWeekend-CPP
Note the CMake version was tested initially with clang 17, and we're already on clang 22, so some of those comments are irrelevant nowadays, I haven't bothered to update the project.
Naturally if you cannot be on latest compiler releases, or suffer from CMake phobia, the support isn't there.
> at work it is a different matter
that's what I was asking, of modules are being introduced at scale or if they are a hobbist thing
https://nibblestew.blogspot.com/2025/08/we-need-to-seriously...
1 reply →