"Trip report: November 2025 ISO C++ standards meeting (Kona, USA)"

From	Lynn McGuire <lynnmcguire5@gmail.com>
Newsgroups	comp.lang.c++
Subject	"Trip report: November 2025 ISO C++ standards meeting (Kona, USA)"
Date	2025-11-11 23:23 -0600
Organization	A noiseless patient Spider
Message-ID	<10f15kk$17ode$2@dont-email.me> (permalink)

Show all headers | View raw

"Trip report: November 2025 ISO C++ standards meeting (Kona, USA)" by 
Herb Sutter
  
https://herbsutter.com/2025/11/10/trip-report-november-2025-iso-c-standards-meeting-kona-usa/

"On Saturday, the ISO C++ committee completed the first of two final 
fit-and-finish meetings for C++26, in our meeting in Kona, USA. What we 
have in the C++26 working draft represents exactly the set of features 
we have consensus on so far; the goal of these last two meetings is to 
fix bugs and otherwise increase consensus for the C++26 standard. We are 
well on track to complete our work on C++26 and set it in stone at our 
next meeting in March 2026."

"For contracts (pre, post, contract_assert), we spent most of Monday and 
Tuesday reviewing feedback. The strong consensus was to keep contracts 
in C++26, but to make two important bug fixes and pursue a way to 
specify “must enforce this assertion”:"

"    We discovered two bugs, and adopted fixes for those at this 
meeting. One was paper P3878R1 “Standard library hardening should not 
use the ‘observe’ semantic” by Ville Voutilainen, Jonathan Wakely, John 
Spicer, and Stephan T. Lavavej.
     For the next meeting in March, we are also pursuing something like 
the first proposed solution in P3911R0 “[basic.contract.eval] Make 
Contracts Reliably Non-Ignorable”by Darius Neațu, Andrei Alexandrescu, 
Lucian Radu Teodorescu, and Radu Nichita (though not necessarily with 
that particular syntax). The idea is to add an option to express in 
source code that a pre/post/contract_assert must be enforced, which some 
view as a necessary option in the initial version of contracts. A group 
of interested persons will work on that design over the winter, 
including to answer questions like “what syntax?” and “should violations 
call the violation handler or not?”, and bring a proposal to the March 
meeting."

One of these days, I will figure out what contracts are again.

Lynn

Back to comp.lang.c++ | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

"Trip report: November 2025 ISO C++ standards meeting (Kona, USA)" Lynn McGuire <lynnmcguire5@gmail.com> - 2025-11-11 23:23 -0600
  Re: "Trip report: November 2025 ISO C++ standards meeting (Kona, USA)" Michael S <already5chosen@yahoo.com> - 2025-11-12 12:29 +0200
    Re: "Trip report: November 2025 ISO C++ standards meeting (Kona, USA)" Lynn McGuire <lynnmcguire5@gmail.com> - 2025-11-12 16:06 -0600
  Re: "Trip report: November 2025 ISO C++ standards meeting (Kona, USA)" Lynn McGuire <lynnmcguire5@gmail.com> - 2025-11-19 13:02 -0600
    Re: "Trip report: November 2025 ISO C++ standards meeting (Kona, USA)" David Brown <david.brown@hesbynett.no> - 2025-11-20 09:31 +0100

csiph-web