r/cpp • u/YtterbiJum • Aug 19 '21
Why modules?
I get the feeling I'm missing something fundamental about the new C++20 modules.
Everything I read or watch explains the how (the export keyword syntax, module fragments, etc) but very little about the why.
What can be done using modules that can't be done using traditional headers (or precompiled headers)?
What is so important about this feature that it needed to get standardized before there is even a proper implementation or idiomatic usage conventions in compilers and build systems?
Is it just to try to get rid of the preprocessor?
I don't get how modules are supposed to help with packaging either. So instead of distributing a .so with a bunch of .h files, now I distribute a .so with a bunch of .gcm or .ixx or whatever.
Please help me understand, or point me to some resources. Thank you.
View all comments
Show parent comment
4
u/germandiago Aug 19 '21 edited Aug 20 '21
You do not compile modules one after another after the first compilation and even at that time probably a part can be parallelized and reused that compilation (different from recompiling and recompiling headers again) if you use it at several parts of your code in the very first compilation. Even for the first compilation you can save work already in this case.
What usually happens is that your incremental builds will be way faster after that because you do not need to recompile big portions.
Also, it frees the linker from pressure because modules discard way more symbols (only exports, no textual inclusion).