C++26 Delayed: Contracts Controversy Derails Final ISO Vote
C++26's ISO DIS vote failed 13-9-12 over the Contracts proposal P2900, with Bjarne Stroustrup calling it an existential threat while others warn a late veto undermines trust; the standard may slip to 2027 as WG21 meets in Brazil to decide whether to drop, defer, or revise Contracts.
The upcoming C++26 standard has hit a major roadblock after its Draft International Standard (DIS) vote at ISO failed in October. The vote tally was 13 in favor, 9 against, and 12 abstentions, falling short of ISO's requirement that opposition not exceed 25%. The primary point of contention is the Contracts feature (proposal P2900), a design-by-contract mechanism allowing preconditions, postconditions, and assertions to catch programming errors that lead to undefined behavior.
What Are Contracts?
Contracts, also known as design by contract, have been a feature of languages like Ada and Eiffel for decades. They let developers specify conditions that must hold at function entry (preconditions) and exit (postconditions), plus general assertions. The goal is to detect bugs early and improve safety. C++ has considered adding contracts for at least ten years; a previous version was removed from C++20 over concerns about dangerous defaults.
The Core Dispute
Bjarne Stroustrup , C++'s creator, strongly opposes the current P2900 proposal. In an August 2023 paper, he and co-authors wrote that "P2900 Contracts and extensions are intended to change the nature of C++, pose an existential threat to C++, and add complexity and bloat." They argue the implementation is messy, outdated, insufficiently tested, and would be more effective as a library.
Opposing this view, committee member Andreas Fertig contends the criticisms have already been reviewed and that vetoing the proposal this late harms C++ itself. He wrote: "This issue has been discussed for years and passed multiple majority votes in its current form. Voting 'no' shakes an established system built on trust and mutual respect."
Harry Bott , CEO of the C++ Alliance and maintainer of the EDG C++ front end, takes a middle stance. He told The Register : "The returned draft is not a failure of process — it is the process working as intended. But that doesn't mean the process can't be improved. Our goal should be to learn from this and strengthen the process so C++ can continue to evolve in a way developers can rely on."
Context: Safety Pressure and Rust
The debate occurs amid broader criticism that C++ makes it too easy to create security vulnerabilities, prompting some projects to adopt Rust. Stroustrup himself notes that adding safety controls could undermine C++'s core advantage: extremely fast development speed.
What Happens Next?
Because the vote failed at a late stage — a rare event in C++ history — the release may miss its 2026 target, potentially becoming "C++27" (formally ISO/IEC 14882:2027). The ISO C++ working group WG21 meets next week in Buzios, Brazil, for a final debate. According to software engineering consultant Thibault Ricord-Marchal, the group faces several options:
Remove Contracts from the specification so the rest of C++26 can ship. This would be laborious, as much library-hardening work using Contracts would need to be undone.
Move Contracts to a separate Technical Specification for further refinement.
Modify the proposal and revote , hoping the Brazilian setting calms tensions.
The outcome will shape not only the next C++ standard but also the governance model of one of the world's most widely used programming languages.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
