C++ Modules and Large-Scale Development
summary
Argues that C++ modules mainly reshape architecture not just compile times, listing concrete requirements: modules must be purely additive, hierarchical, incremental and interoperable so teams can adopt them without changing legacy code. Specifies design rules modules must enforce—no cyclic physical dependencies, no long‑distance friendship, no brittle transitive includes—and notes limits: modules do not magically provide insulation so the pimple idiom still applies and macros (e.g. loggers) must remain supported.
AI-written summary · about
chapters (6)
- 0:00Introduction and welcome
- 1:44Components and modules basics
- 23:55Essential physical design rules
- 34:21Insulation and encapsulation in modules
- 42:44Requirements for C++ modules
- 55:04Q&A session
related talks
01h 30mC++ Modules and Large-Scale Development
01h 30mC++ Modules and Large-Scale Development
01h 01mLarge Scale C++ with Modules: What You Should Know
01h 04mProgramming with C++ Modules: Guide for the Working
58mWhy Modules?: It's not about build time
59m“There and Back Again: An Incremental C++ Modules Design"
01h 37mC++ And Beyond: Discussion
01h 10m“C++ Modules: The State of The Union"