deniz.in

Markets

Weather

Loading weather

· via Hacker News – Front Page (native)

C++26 technical work recompleted after failed ballot; second ISO vote expected

The ISO C++ committee has finished technical work on C++26 for a second time after its first approval ballot failed over concerns about the contracts feature, and will issue an updated draft for a new vote.

C++26 technical work recompleted after failed ballot; second ISO vote expected

C++26 is finished, again

According to Herb Sutter's trip report on the November 2026 ISO C++ standards meeting in Búzios, Brazil, the committee has recompleted technical work on C++26. The standard was originally declared technically complete at the March 2026 meeting, but the subsequent international approval ballot — the Draft International Standard (DIS) vote — did not pass, sending the draft back with additional national body comments to resolve. The committee spent most of its six-day session addressing those comments and now expects to produce an updated document for a second DIS ballot, followed by final editorial work and ISO publication.

Why the first ballot failed

Sutter writes that the ballot comments were overwhelmingly about contracts, the C++26 feature adding pre, post and contract_assert constructs for expressing and checking function expectations. The committee has had strong internal consensus on the feature throughout: a February 2025 plenary vote to merge contracts into the working draft passed 100 to 14 with 12 abstentions (87.7% in favor), and the March 2026 vote to finalize the standard passed 114 to 12 with 3 abstentions (90.5%).

But during the DIS process, five national bodies raised contracts concerns for the first time and voted Disapprove. Sutter notes that every previous C++ DIS ballot had been unanimous, and that the result surprised nearly everyone involved.

This week's vote to reship the standard, including a new contracts extension and keeping the feature in C++26, passed 111 to 9 with 8 abstentions (92.5%). Several ballot comments had asked for contracts to be removed entirely; the committee discussed those requests, revoted, and reaffirmed its decision to retain the feature.

What changed this week

Four main papers were adopted for C++26, along with editorial fixes, and all were also applied to draft C++29 to keep the two tracks in sync rather than forking them.

The headline change is P4451R2, "Early Adoption of an Always-Enforced Label" by Joshua Berne, which Sutter describes as similar in spirit to Romania's P3911R2. It is a pure extension that lets programmers mark a specific contract assertion as always enforced, guaranteeing that program execution will not continue past that assertion if it is violated, regardless of how other parts of the program were built. Sutter says this answers what several national bodies identified as their primary request for contracts, and the design remains forward-compatible with proposals being considered for C++29.

The other adopted papers:

  • P4466R2, selectively transparent using-declarators by Dan Katz and Tomasz Kamiński, which makes reflection work more consistently with modules, including module std, while leaving fuller using-alias reflection support for C++29.
  • P4453R1 on memory allocation with senders and receivers by Dietmar Kühl and Lucian Radu Teodorescu, giving more flexible control over allocation in std::execution.
  • P3861R1, a pragmatic approach to standard structural types by Corentin Jabot, which expands where string_view, span and tuple can be used, including as template parameters, and enables type-safe compile-time strings for reflection.

C++29 work continues

Alongside the C++26 fixes, the committee adopted features for draft C++29, including labeled break and continue statements, std::ranges::any_view, views::slice, and more. The meeting was hosted by the C++ Alliance, with Matheus Izvekov leading local arrangements. Around 220 attendees represented 27 nations, split roughly 35% in person and 65% remote — a higher remote share than usual, partly because a U.S. aviation ground stop disrupted travel just as experts were flying out. Of the committee's 22 active subgroups, fewer than usual met, as the week focused on the C++26 comments.

Why it matters

A failed DIS ballot is unprecedented for C++, and it demonstrates that national body review can force the committee back to the table even after strong internal supermajorities. The resolution is notable for its shape: rather than stripping out contracts, the most contested and arguably most significant feature in C++26, the committee adopted an extension that makes individual contract assertions reliably enforceable, directly addressing the stated objection. If the second ballot succeeds, compiler vendors, library authors and standards bodies can finally plan against a stable C++26 feature set — and the episode itself becomes a data point in how ISO language standards get negotiated.

  • #c-plus-plus
  • #c-plus-plus-26
  • #iso-standards
  • #contracts
  • #programming-languages