C++26 Ballot Fails Over Contracts Dispute
By @sharedot · · 6 pages
- Programming
- C
- Iso Standards
The C++26 Draft International Standard failed its October ISO ballot over the disputed P2900 Contracts proposal, casting doubt on the 2026 release.
The ballot that stunned the committee
The Draft International Standard of C++26 failed its ISO ballot in October, with 13 votes in favor, 9 against and 12 abstentions. ISO rules cap negative votes at 25 percent, so the result fell short — a rarity this late in the standardization process.
Contracts, the security-enhancing feature at the center of the fight, was the major sticking point for those voting nay.
Stroustrup versus the committee
C++ creator Bjarne Stroustrup and colleagues called proposal P2900 an existential threat to the language in an August paper, citing complexity, bloat, limited testing and arguing the checks could be a library instead.
Committee member Andreas Fertig, per both The Register and LavX News, says the topic was vetted for years and approved multiple times, warning a late rejection shakes a system built on trust. The C++ Alliance's Harry Bott told The Register the failed ballot is the process working as intended.
Why Contracts cut so deep
Contracts let developers declare preconditions, postconditions and assertions that check program state at defined points, catching bugs that would otherwise lead to undefined behavior and security holes — a weakness that has pushed projects toward Rust.
A previous Contracts attempt was yanked from C++20 over dangerous defaults.
Three paths in Búzios
WG21 meets next week in Búzios, Brazil.
According to consultant Thibault Ricord-Marchal, cited by both outlets, the options are carving Contracts out of the spec (messy, since library hardening already depends on it), moving Contracts to a separate technical specification, or a minor revision and a re-vote.
If the 2026 window is missed, the informal name becomes C++27, officially ISO/IEC 14882:2027.