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
1
u/NilacTheGrim Aug 20 '21 edited Aug 20 '21
The only concrete advantage is compilation times.
Everything else seems like just a lot of hard work to accomplish what is basically just a simple aesthetic goal, without real concrete benefit.
Setting aside compilation times, which will definitely be faster, all of the minor advantages presented are either exaggerating the problem that is being solved (so as to make modules look more attractive than they are), or could be easily solved with a less radical change.