Demystifying the C++ Committee
summary
Explains how C++ changes actually get into the standard: write a paper, implement it in a compiler or library, get it through Evolution (syntax) or Library Evolution, then through Core/Library wording groups and the plenary for a vote; guests may attend subgroup sessions and debate but guests cannot vote. Committee is WG21, holds three meetings a year with good remote access and Sunday orientation, runs focused study groups (SG7, SG21, modules, concurrency), and publishes the latest drafts free on isocpp.org; even tiny edits like allowing mutable lambdas without empty parentheses follow this pipeline.
AI-written summary · about
chapters (9)
- 0:00C++ Committee intro
- 2:17ISO structure and WGs
- 3:40Standard C++ Foundation role
- 7:13C++ Standard document
- 8:42Committee groups and proposals
- 12:11Study groups purpose
- 13:17Guest at meetings
- 16:52Becoming full member
- 17:57Call to action
related talks
01h 25mGrill the C++ Committee
07mC++ Standardization
01h 25mGrill the C++ committee
01h 01mC++ Committee's Library Evolution Working Group
01h 03mC++ Standards Committee Fireside Chat
01h 33mCommittee Fireside Chat
03mThe Beman Project: Testing C++ Library Proposals Before Standardization
01h 09mC is So Back: Unbreaking the Charter