ISO C++ Standards Committee Panel Discussion 2024
summary
Panelists list concrete progress and pain points: C++26 aims to ship contracts and reflection but contracts split across many purposes (about 196 use cases), reflection drops expression-level introspection for now, and executors/std::execution plus sender/receiver work is practically implemented by some vendors. Proposals try real fixes—profiles for safety, linker-aware optimizations, exception-cost reductions—and shipping cadence (roughly every three years) forces tradeoffs; networking took ~15 years, and compiler frontend differences make implementation engineering the hardest gap to close.
AI-written summary · about
chapters (17)
- 0:00Welcome
- 3:54Top C++26 features
- 7:27Big features standardization delay
- 14:15C++ standardization process
- 21:19Idea to standard feature
- 31:39Memory safety vs Rust
- 38:03Safety in critical systems
- 42:42Government pressure on C++
- 50:55Reflection and static analysis
- 56:33Proposals and future communities
- 1:00:14Linkers and low-level optimizations
- 1:03:27Undefined behavior and type punning
- 1:07:06Single compiler standardization
- 1:14:20Committee reflections
- 1:15:24Joining the committee
- 1:21:43Formal methods in C++
- 1:27:45Future C++ proposals
related talks
01h 26mGrill The Committee Panel
01h 37mC++ And Beyond: Discussion
01h 02mC++ Committee's Library Evolution Working Group Panel
01h 31m“Grill the Committee”
01h 14m"Technical Specifications & C++17"
58m"WG21-SG14 – Making C++ better for games, embedded and financial developers"
13mThis Is C++ - Exclusive Interview With Jon Kalb ( CppCon Conference Chair ) - C++OnSea 2024 Preview
01h 31mWhat C++ Needs to be Safe