Skip to content
C++26 Contracts Proposal Rejected in ISO Vote, Standard Delayed

C++26 Contracts Proposal Rejected in ISO Vote, Standard Delayed

The ISO vote on C++26's contracts proposal failed, with P members achieving only 60% approval (needed 66.66%) and member bodies registering 41% opposition (exceeding 25% threshold), marking the first time a C++ standard failed to pass unanimously; the November meeting will decide next steps.

21CTO
21CTO
21CTO

On October 24 (local time), the International Organization for Standardization (ISO) voted on the contracts proposal for C++26. The proposal was rejected because neither voting group reached the required threshold.

Voting Results

P members (principal members): 12 out of 20 voted yes (60%). The required supermajority is 66.66%. Twelve P members abstained; their votes were not counted.

Member bodies: 9 out of 22 voted no (41%). The requirement is that no votes must not exceed 25%.

Robert Seacord posted the results on the committee mailing list, calling it "somewhat of a sad day for the C++ community."

Community Reactions

Harald Achitz argued the outcome reflects a healthy, engaged community: "Given the number of P members who abstained due to lack of consensus — which makes the no votes more meaningful — rejecting a flawed contracts proposal is a positive signal from a good, active, and capable national-body-level community."
J. Daniel Garcia highlighted the 12 abstentions as evidence of controversy: "In several cases, this was because they could not reach a common position. Note that before C++26, all other standards passed unanimously."

Steve Downey noted an arithmetic inconsistency between the two voting groups: 8 no votes from P members versus 9 no votes from member bodies, though he acknowledged the gap is not material because the result was not close.

Roger Scott suggested narrowing the scope as the most promising path forward: "Is the most promising way forward to narrow the scope and try again?"

René Ferdinand Rivera Morell asked what lessons should be learned to move forward productively; Lieven De Cock expressed similar sentiments about learning and regrouping.

Historical Context

This result marks the first time in C++ history that a standard failed to achieve unanimous approval. All previous C++ standards passed unanimously.

Next Steps

The next full committee meeting is scheduled for November. It remains undecided whether the contracts feature will be removed or put to a revote. Experimental implementations of contracts in C++ compilers remain available for use, but developers should monitor further adjustments to the draft.

Voting results breakdown
Voting results breakdown
Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

C++26C++ standards committeecontracts proposalISO standardizationprogramming language governanceWG21
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.