Why Modules?: It's not about build time

on YouTube ↗58m

" summary

Named modules shift C++ from build optimization to fine-grained control visibility by using module interface and implementation units, partitions, and a private fragment to hide internals while exporting only selected declarations. The compiler produces a BMI and mangles the module name into symbols, so ABI changes if an entity moves modules; compiled module interfaces are fragile across compiler flags and versions and can refuse to import. Dependency cycles are forbidden, forward declarations across modules are not allowed, and real examples like libfmt work but require careful build consistency.

AI-written summary · about

" chapters (13)

1. 0:00Introduction to modules
2. 1:02Purpose and goals
3. 2:08The problem with include
4. 7:59Core benefits of modules
5. 12:17Module syntax and structure
6. 18:17Purview, export, and import
7. 23:36Legacy and private fragments
8. 26:44Reachability and partitions
9. 30:24Managing project dependencies
10. 36:28Advanced module techniques
11. 39:11ABI and link-time impacts
12. 45:24Testing strategies
13. 48:41Q&A and conclusion

" related talks

• 32mVisibility, Reachability, Linkage – The Three Secret Spices of C++ ModulesDaniela Engert · Pure Virtual C++ 2021
• 01h 30mC++ Modules and Large-Scale DevelopmentJohn Lakos · ACCU 2018
• 01h 04mBuilding ModulesMichael Spencer · CppCon 2019
• 01h 01mLarge Scale C++ with Modules: What You Should KnowGabriel Dos Reis · CppCon 2015
• 01h 04mProgramming with C++ Modules: Guide for the WorkingGabriel Dos Reis · CppCon 2019
• 01h 01mC++20 Modules - Review of the Current State of C++ Modules 2024Luis Caro Campos · C++ on Sea 2024
• 59mC++ Modules and Large-Scale DevelopmentJohn Lakos · CppCon 2018
• 01h 30mC++ Modules and Large-Scale DevelopmentJohn Lakos · ACCU Autumn 2019 Belfast