“C++ Modules: The State of The Union"
summary
Claims that C++ modules are moving from proposal to a TS with real compiler support: MSVC and Clang already implement parts, Visual Studio 15 will ship module work, and a persistent IFC on-disk metadata format stores an abstract semantics graph so tools can share interfaces. Templates export with the export keyword, macros are contained, and name lookup stays familiar. Measured internal build improvements reach 10–17x internal speedups and the target is 5–10x widely; the module surface is just module import export and the design interoperates with headers.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:55Modules update
- 2:28Committee and implementation
- 5:51Compilers and support
- 9:36Module goals
- 15:01Module syntax and usage
- 19:01Technical details
- 24:09Working with modules
- 25:39Standard library modules
- 29:00Language rule changes
- 34:07Transitional paths
- 36:25Future opportunities
- 42:01Shared representation
- 46:48IFC format details
- 49:41Q&A session
related talks
36mC++ Modules: Year 2021
34mPractical C++20 Modules and the future of tooling around C++ Modules
58mKnockin' on Header's Door: An Overview of C++ Modules
01h 11mA Practical Introduction to C++20's Modules
01h 00mAdding C++ modules-ts to the GNU Compiler
05mAre We Ready for Modules in C++?
59mC++ Modules and Large-Scale Development
01h 01mPractical C++ Modules