ISO National Bodies Reject C++26 DIS Over Contracts Integration
The Draft International Standard for C++26 has failed its ISO ballot after failing to secure a two-thirds majority due to National Body objections regarding Contracts. The rejection halts the standard's approval pipeline and forces ISO WG21 into an administrative impasse ahead of its November 16, 2026 meeting.
Unprecedented Failure at the DIS Stage
On October 23, 2026, ISO National Bodies (NBs) voted to disapprove the C++26 Draft International Standard (DIS) following a twelve-week voting window. Under ISO procedures, the DIS phase is the penultimate stage before publication and requires a two-thirds majority to pass. The C++26 DIS failed to achieve this threshold.
This is the first time in the history of the core C++ language standard that a DIS ballot has failed. Within the ISO system, the only similar precedent occurred on August 11, 2006, when ISO/IEC DIS 26926 (C++/CLI Language Specification) failed approval and was subsequently halted.
The Central Conflict: Contracts Specification
Feedback submitted with the negative NB votes indicates that the rejection was driven by the inclusion of Contracts, with dissenting National Bodies arguing that the feature is not ready for standardized release.
- 2019: Added to the C++20 draft during the Cologne meeting, but removed later in the same session.
- 2020–2024: Subjected to a dedicated Study Group before being referred to the Evolution Working Group (EWG) for language extension review.
- March 2026: Included in the C++26 draft and approved by WG21 with a substantial majority to proceed to the DIS stage.
Historically, National Bodies only voted against a DIS if procedural errors occurred or new technical information surfaced. In this vote, dissenting NBs cited new papers containing existing arguments to justify their opposition, overriding the committee's earlier majority decisions.
Procedural Options and Reconstitution Risks
Under ISO rules, WG21 must select one of four formal routes forward: 1. Submit a revised draft for a second DIS vote. 2. Revert the draft back to the Committee Draft (CD) phase. 3. Publish the draft as an intermediate Technical Specification (TS). 4. Cancel the C++26 project entirely.
Navigating any of these options presents procedural hurdles, as each requires a majority vote within WG21. The committee voted by more than a two-thirds majority to advance C++26 with Contracts, meaning members who authored and approved the feature are unlikely to willingly discard their work. Conversely, opposing NBs are unlikely to approve a revised DIS without the removal of Contracts.
If the committee elects to cancel the project, the standard baseline will revert to C++23, pushing all forward progress to C++29. This action would not automatically port existing C++26 features; every non-controversial feature would require individual author advocacy and fresh papers to be incorporated into the C++29 draft.
Deadlock Prior to the November Session
The DIS failure destabilizes the consensus-based trust model essential to ISO standardize workflows. WG21 will convene on November 16, 2026, to attempt to resolve the impasse. Until the committee establishes a viable strategy regarding Contracts, work on the current draft and future planning for C++29 remains at a standstill.