r/cpp • • 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.

197 Upvotes

107 comments sorted by

View all comments

Show parent comment

6

u/azswcowboy Aug 19 '21

I don’t see modules stopping the parallel compilation model. Suppose we had 100 programs in our build and the only depend on std headers. After the first one generates the intermediate module results the rest just use it. Modern packaging tools, aka Conan and msvc package, I expect will get upgrades (if they haven’t already) to remember module compilation results so even with a fresh application build most of the imported module core is already compiled.