It’ll be nice when this can be reliably used. According to cppreference MSVC has partial support and other compilers have zero support.
I’m not sure modules will be in widespread use before 2029.
GCC is getting there.
clang, well they seem stuck with their own initial modules implementation (module maps based), and now with Apple and Google out of the picture, the various compiler vendors that benefit from MIT license don't seem that eager to contribute to upstream other than LLVM.
Unfortunely everyone else seem to still be catching up with C++14 and C++17, depending on the ecosystem.
No, but the code I write for my job does have to be cross-platform from day 0. And that's the code base that is large enough where module improvements to compile time would be most useful! Hobby projects are small enough it's not super important.
So C++20 modules don't help me and probably won't until 2029! To my great dismay.
However I agree it is a bummer for cross-platform code and there is a ton of it, with clang being the major culprit holding C++20 back.
So that covers projects funded by Microsoft and… almost nothing else. Because if you can ship on Xbox you’d probably be smart to ship on PlayStation and possibly Switch.
The number of real projects that can use modules isn’t zero. But it’s pretty god damn close! This ain’t the hill to die on.
Which ironically, both Playstation and Nintendo win over XBox in exclusive titles.
> many studios actually enjoy the perks that come with being platform exclusives
Yes, building a game for a single fixed piece of hardware is great fun. But we live in the cross-platform age. As practical matter the Xbox One and Xbox Series Blah are losers. Shipping for Xbox but not Playstation (and often times Switch) is just leaving money on the table.
The list of “games released only on Windows and Xbox” is very small.
You're right. My project is not one of those projects.
As mentioned in the article, the C++ project has no dependencies (outside googletest and the standard library, whose build time isn't included in the benchmarks).
Also, the project is relatively light on templates compared to most C++ code that I've seen. The biggest offenders are narrow_cast and vector.
> Also at least in VC++, modules are already a thing
I'd love to use them, but I mostly work on Linux and macOS. =[
> Still looking forward to binary libraries support in cargo (well one can dream).
I didn't consider this downside of Rust! I imagine rlibs can be cached manually, right? I don't know if rlibs are portable between machines.
Is this not what sccache is already doing?
I don't understand how conan managed to get so much traction, it is so very bad, most of its recipes have billions of options most of which don't work.
The only sensible way to work with C++ is to always build from source, and let the build system transparently cache and reuse binary artifacts as an optimization.
Then again, it isn't something that is relevant in GNU/Linux world, only in other platforms.
You would still build your code from source, and be very careful handling any dependencies you don't have the source for.
The worst kind of undefined behaviour you can have in C++ is ODR violations, and importing binaries is more likely than not to trigger them, unless you closely manage their ABI.
Also at least in VC++, modules are already a thing, no need to keep parsing template code all the time.
Doing a C++23 import std (which imports the whole standard library) takes a fraction of the time of #include <iostream> in VC++.
So a clean build out from repo means compiling only our own code, not the whole world as in Rust.
Still looking forward to binary libraries support in cargo (well one can dream).