C++26 Disapproved
Web page · https://andreasfertig.com/blog/2026/11/cpp26-dis-failed-how-does-cpp-survive
First seen by Oriel on .
AI summary
The C++26 ISO DIS failed because National Bodies rejected its Contracts feature, leaving WG21 to choose a delayed revision, Technical Specification, or cancellation while trust and C++29 work are affected.
- The DIS requires a two-thirds majority, which was not achieved after a twelve-week National Body voting period.
- Contracts entered C++26 after years of study and multiple WG21 approvals, including the March 2026 draft vote.
- ISO offers four paths: a revised DIS, a revised committee draft, a Technical Specification, or project cancellation.
- Each option requires WG21 approval and delays the next C++ standard; cancellation would revert to C++23 and target C++29.
- The November 16 meeting is expected to address the deadlock, with possible consequences for C++29 and the committee’s trust-based collaboration.
#c++ #contracts #iso standardization
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Hacker News: 408, latest observation ; +398 over observed period since
- Lobsters: 43, latest observation ; +41 over observed period since
Comments
Comment count reported by the source.
- Hacker News: 351, latest observation ; +351 over observed period since
- Lobsters: 33, latest observation ; +33 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Hacker News | 50360164 | https://andreasfertig.com/blog/2026/11/cpp26-dis-failed-how-does-cpp-survive/ Read discussion |
| Lobsters | xvtufg | https://andreasfertig.com/blog/2026/11/cpp26-dis-failed-how-does-cpp-survive/ Read discussion |