C++26 Disapproved

On October 23, 2026, the C++ Standardization Committee (WG21) faced a significant setback when C++26 was disapproved in a vote by ISO National Bodies (NBs). This marks the first time in the history of C++ that a DIS ballot failed. The process involves approval, rejection, or abstention, with a two-thirds majority required. The reason for the rejection was due to contracts, with many NBs believing the feature was not ready for release.

The C++ Standardization Committee follows ISO rules but has additional rules, such as hearing opinions when new information becomes available. The previous practice was to only vote against a standard if new information became available or if errors in the process were identified. However, this changed on October 23, 2026. The NBs who want C++26 without Contracts argue that there is new information, but the author finds this hard to agree with.

Contracts have been on the wish list for a long time and were included in C++26 after a majority vote. The next step was DIS, where enough "no" votes were received for the majority required not to be achieved. The author suggests that several options are available, all of which involve delays in the next C++ standard. The issue is that they all require a majority within WG21, and the working group has already voted to move C++26 with Contracts into the next voting phase.

The author believes it would be difficult for the group to abandon its work, and removing Contracts would require a majority vote in WG21. The future of C++ is currently at an impasse, with the next meeting set for November 16.