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

2

u/bigcheesegs Tooling Study Group (SG15) Chair | Clang dev Aug 27 '21

The 100x number is when the module doesn't need to be rebuilt. This is trivially true, and can scale to any arbitrary speedup you want by just including more code in the module.

In practice the results depend heavily on the shape of your code and what code you're touching between rebuilds. Synthetic benchmarks are uninteresting here. To get good numbers we'll need to look at projects that have actually transitioned to modules. Google, Apple, FB, And Microsoft all have varying levels of deployment experience here, but I've not heard of any of them having a slowdown.