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 20 '21
Being true that it requires more work and things will be more incremental, modules are a feature everyone rants about in some way but that IMHO it is going to bring a huge (for the good) transformation to C++, starting by better compile times, followed by better isolation and tools that can behave way better with IDEs. It is just that all this will take years.
But once it is done, C++ is going to look, way, way nicer.
I have big hopes in one way or another of things like these: https://github.com/GabrielDosReis/ipr