C++26 Disapproved

C++26 failed its ISO Draft International Standard (DIS) ballot on October 23, 2026, reportedly the first failed DIS vote in the language’s history. Approval required a two-thirds majority, and national bodies’ objections centered on Contracts: some judged the feature not ready for standardization. Contracts had been developed and debated for years, removed from C++20, revised through a study group, and later approved by substantial majorities in WG21, including when the C++26 draft advanced in March 2026. The author, a WG21 participant who helped represent Germany, argues that the rejection departed from the committee’s usual practice of opposing a draft only when genuinely new information or procedural problems emerge; in his view, repeating earlier objections undermines the established process.

The failure leaves the standard’s path uncertain because every available remedy needs renewed support within WG21, where opponents and advocates have both invested heavily in their positions. Options include revising the draft for another DIS vote, returning it to committee review, issuing a Technical Specification, or canceling the project. Each would delay the next standard; cancellation could mean reverting to C++23 and rebuilding C++29 from individual proposals, risking the loss of already approved work. The author sees the immediate challenge as finding a way past the deadlock at the November 16 meeting, with consequences for C++29 as well. More broadly, he argues that standards depend on compromise and trust, and that rejecting a repeatedly approved feature has damaged both, leaving the community needing to restore confidence before it can move forward.