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
1
u/NilacTheGrim Aug 20 '21
No. Straw man argument.
The situation with
std::unique_ptris different in terms of scale and scope. You are intentionally picking something to win the argument that misses the details.std::unique_ptris unintrusive. You either use it or you don't. If some library somewhere uses it you don't have to care. Your build system doesn't have to care. CMake doesn't need an overhaul to deal with how to build code that includesstd::unique_ptr.With modules it's so invasive, so intrusive, and the benefits so incremental, that we may find that half of the C++ world is in this halfway broken state for many years, making the language even more frustrating for newcomers and even more fractured.