Programming with C++ Modules: Guide for the Working
summary
Modules become first-class in C++20 and promise big compile-time wins: the compiler writes a binary module description so modules compile once and reuse metadata, cutting repeated header parsing and giving up to an order-of-magnitude speedups in tests. Strategies include module interfaces, implementation units, partitions, global module fragments to wrap messy C headers, and header units as a standardized PCH. Implementations exist in MSVC/Clang/GCC branches; tooling and build-order support still need work.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:00Challenges
- 4:00Progress
- 6:35What did we get
- 10:20How does it work
- 13:35Compiler Firewall
- 16:40Modules
- 28:55Module Aggregation
- 30:35Global Fragments
- 34:15Conditional Tools
- 36:00Header Files
- 40:35When to use Header Units
- 42:35Macros and Header Units
- 46:45Source File Organization
- 48:25Build System
- 49:40Download C Modules
- 50:50Upcoming Modules Talks
- 52:20Build Time Improvements
related talks
01h 01mLarge Scale C++ with Modules: What You Should Know
01h 30mC++ Modules and Large-Scale Development
01h 30mC++ Modules and Large-Scale Development
36mC++ Modules: Year 2021
59mC++ Modules and Large-Scale Development
01h 01mC++20 Modules - Review of the Current State of C++ Modules 2024
58mWhy Modules?: It's not about build time
32mVisibility, Reachability, Linkage – The Three Secret Spices of C++ Modules