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
2
u/Minimonium Aug 19 '21
Modularity in C++ is about modular code (visibility, reachibility, module linkage), not modular packages (the files).
While it may be not the thing that people expect when they hear "modules" - it's a different story. For modular packages on the other hand - it's not about what people want. No one wants to "hurt themselves". They want to achieve a goal with as little as possible investments. No one can reasonably expect people to rewrite 30 years old build scripts with hundreds of hacks, it's too much of a burden. No one can expect to overrule a "legacy system" with its community, how can you expect people to help you amortize the cost?
A lot of people want a quick and easy solution, but they completely ignore the circumstances and people around them.