C++26 Disapproved
- ID
- 42875
- Status
- summarized
- Published
- 04 Nov 2026, 8:33 AM
- Fetched
- 04 Nov 2026, 7:26 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://andreasfertig.com/blog/2026/11/cpp26-dis-failed-how-does-cpp-survive/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 04 Nov 2026, 7:26 PM
- Tags
- Audience
- developers
What happened
On 23 October 2026, ISO National Bodies disapproved the C++26 DIS after a 12-week ballot; a two-thirds majority was required but not reached, and the comments point to Contracts as not ready. Andreas Fertig, a C++ standardization committee member who represents Germany's vote, writes that this is the first failed C++ DIS ballot he could find apart from C++/CLI's DIS 26926 in 2006, which was halted. The HN thread drew 314 points and 207 comments.
Why it matters
If you ship C++ or depend on C++ toolchains, do not plan migrations around C++26 Contracts or assume the standard's timetable: Contracts is the blocker and the ballot failed. Keep using existing contract mechanisms and wait for WG21/national-body follow-up before changing compiler baselines; for AI/ML and SaaS stacks without C++ in the critical path, there is no direct action.
Discussion angle
What should teams do with C++26 now: freeze the toolchain, adopt a contracts library, or wait for WG21's next move—and what would make you change that decision?