A (Short) Tour of C++ Modules
summary
Shows how C++ modules work in practice: the distinction between a primary module interface and separate implementation units, the purpose of the global module fragment, and exactly when export makes declarations visible. Explains how compilers save a compilation-state index so clients can consume prebuilt module interfaces instead of reparsing headers (reducing rebuild work), and walks migration pitfalls (templates, linkage, header-only libraries), current toolchain support (MSVC/Clang/GCC experimental), and end-to-end examples.
AI-written summary · about
chapters (9)
- 0:00C++ modules intro
- 6:14Compilation issues solved
- 13:10Module design benefits
- 20:44Interface visibility
- 28:25Strong ownership model
- 35:00Performance impact
- 41:15Compilation times
- 47:13Adoption factors
- 52:46Summary
related talks
01h 03mSo, you want to use C++ Modules ...cross platform
01h 07mModular Code with Examples in C#
01h 00mBack to the basics: Namespaces 101
01h 38mProgramming in the Large With C++ 20
37mA Complete Journey of Android Modularisation
18mModules are not what you think they are
46mFrom Chaos to Cohesion: Building Modular Monoliths in the Real World
56mComponents and Modules