The standardization process for C++26 has reached a critical impasse, casting doubt on the release timeline for the next iteration of the programming language. In October, the Draft International Standard for C++26 failed to secure the necessary support during an ISO ballot, marking a rare setback in the language’s development history. The proposal failed to meet the requirement that no more than 25 percent of votes be cast in opposition, with the final tally showing 13 votes in favor, 9 against, and 12 abstentions.
The primary point of contention is the inclusion of a "Contracts" feature, a mechanism designed to allow developers to define preconditions, postconditions, and assertions within their code. While such features are intended to help identify programming errors that could lead to undefined behavior—a common source of security vulnerabilities in C++—the implementation proposed for C++26 has triggered a deep divide among technical maintainers.
The current proposal, identified as P2900, has faced significant pushback from C++ creator Bjarne Stroustrup and his colleagues. Critics of the proposal argue that the implementation is overly complex, poorly tested, and potentially detrimental to the language's performance and design philosophy. Stroustrup has characterized the current iteration of Contracts as an existential threat to the language, suggesting that the functionality could be more effectively delivered as a library rather than a core language feature.
Conversely, proponents of the feature argue that the proposal has already undergone years of development and multiple rounds of approval. Supporters of the current draft contend that the late-stage opposition undermines the collaborative process of the ISO working group. They argue that the failure of the ballot is a disruption to a system that has historically relied on consensus and compromise, and that the rejection of a previously vetted proposal damages the credibility of the standardization effort.
Other observers within the industry maintain a more neutral perspective, suggesting that the ballot failure is evidence of the standardization process functioning as intended. From this viewpoint, the rejection of the draft is not a sign of systemic failure but a necessary check to ensure that the final standard remains reliable and well-vetted. This perspective emphasizes that the process, while currently contentious, is designed to handle such disagreements before a final version is codified.
The failure to pass the ballot creates significant uncertainty regarding the release schedule. If the working group cannot resolve the dispute quickly, the language may miss its target shipping date, effectively pushing the release into 2027. Should this occur, the official designation for the eighth version of the language would become ISO/IEC 14882:2027.
The ISO C++ working group, known as WG21, is scheduled to meet in Búzios, Brazil, to determine the path forward. The group faces several potential resolutions, including the removal of the Contracts feature from the C++26 specification to allow the remainder of the standard to proceed. However, this approach would be technically difficult, as it would require reversing significant library hardening efforts that have already been implemented based on the proposed Contracts feature.
Alternative strategies include moving the Contracts feature into a separate technical specification for further refinement or performing a minor revision of the current proposal to address the concerns of the dissenting parties. The outcome of the upcoming meeting will be decisive in determining whether C++26 can be finalized in its current form or if the language will face a formal delay.





