› N5048 2026-06 WG21 Admin telecon G. Davidson
› N5049 WG21 2026-06 Brno Admin Telecon Minutes B. Ganetsky
Abstract
Hosting us in Mendel University. We have great facilities available. All study group chairs should register their interest for their room usage at their earliest convenience. We will have a Sunday evening 6:00 PM introductory meeting, as usual. We will have a collective walk from the preferred hotel to the university at 5:30 PM. The usual pre-meeting “read all the papers” email, as soon as the min
› N5050 Working Draft, Programming Languages -- C++ T. Köppe
› N5051 Editors' Report, Programming Languages -- C++ T. Köppe
› N5053 WG21 2026-06 Brno Hybrid Meeting Minutes B. Ganetsky
Abstract
Nina Ranns presents. Every participant is responsible for understanding and abiding by the following:
› N5054 Working Draft, Programming Languages -- C++ T. Köppe
› N5055 Editors' Report, Programming Languages -- C++ T. Köppe
› P2414R12 Pointer lifetime-end zap proposed solutions P. McKenney , M. Michael , J. Maurer , P. Sewell , M. Uecker , H. Boehm , H. Tong , N. Douglas , T. Rodgers , W. Deacon , M. Wong , D. Goldblatt , K. Serebryany , A. Williams , T. Scogland , J. Bastien , D. Krügler , D. Tenty
Author(s)
Paul E. McKenney , Maged Michael , Jens Maurer , Peter Sewell , Martin Uecker , Hans Boehm , Hubert Tong , Niall Douglas , Thomas Rodgers , Will Deacon , Michael Wong , David Goldblatt , Kostya Serebryany , Anthony Williams , Tom Scogland , JF Bastien , Daniel Krügler , David Tenty
Disposition Date
2026-06
Abstract
The C++ standard currently specifies that all pointers to an object become invalid at the end of its lifetime [basic.life]. Although this permits additional diagnostics and optimizations which might be of some value, it is not consistent with long-standing usage, especially for a range of concurrent and sequential algorithms that rely on loads, stores, equality comparisons, and even dereferencing
› P3428R4 Hazard Pointer Batches M. Michael , M. Wong , P. McKenney
Disposition Date
2026-06
Abstract
This paper proposes extending the C++26 hazard pointer interface to support creation and destruction of batches of nonempty hazard pointers. This revision P3428R4 revises R3 by following LWG Brno 2026 feedback.
› P3540R3 #embed Parameter offset J. Meneide
Disposition Date
2026-06
Abstract
The goal is to add the extremely-popular and already-implemented `gnu::offset` and `clang::offset` parameters as standard parameters. That is the only motivation of this proposal; to standardize existing practice.
› P4133R0 Should WG21 Even See This Paper? Admission Gates for Library and Language Proposals V. Falco
Intent
Inform
Abstract
The committee has never established a criterion for what belongs in the standard library. This paper supplies one.
› P4139R3 Better Name for Better Lookups in P3091 N. Myers , P. Halpern
Abstract
[[P3091R5]](https://wg21.link/p3091r5), forwarded to LWG for C++29, adds member functions `get` to associative containers in the Standard Library. These member functions work like `operator[]` or `at`, but return an `optional<T&>` value instead of a simple reference; when lookup fails, they return the empty object. While the feature was strongly favored, support for the name `get` yielded only a w
› P4258R0 C++ Standard Library Ready Issues to be moved in Brno, Jun. 2026 J. Wakely
Disposition Date
2026-06
Abstract
- Ready Issues - 3417. Missing volatile atomic deprecations - 4125. move_iterator 's default constructor should be constrained - 4158. `packaged_task::operator=` should abandon its shared state - 4182. Definition of `NULL` is too broad - 4218. Constraint recursion in `basic_const_iterator`'s relational operators due to ADL + CWG 2369 - 4249. The past end issue for `lazy_split_view` - 4267. Uses-al
› P4268R0 Implementation considerations of library constexpr-ification L. Dionne
Abstract
A wave of recent proposals targets parts of the standard library for `constexpr`-ification. Some of them have already been adopted in C++26, others are being considered for C++29. These papers are often perceived as straightforward, since they are only sprinkling `constexpr` around the standard library. However, in practice, these papers may involve subtle tradeofs for standard libraries and their
› P4302R0 Require One Published Mailing Before Any Poll V. Falco
Intent
Ask
Abstract
The committee takes recorded polls on paper revisions that were never published in a mailing.
› P4306R0 Configuring Runtime Checking: Profiles and Implicit Contract Assertions V. Falco , V. Voutilainen
Intent
Inform
Abstract
Measured against the committee's own criteria, none of them awards ownership of runtime-checking configuration to either proposal.
› P4310R0 Hasta la Vista, Undefined Behavior: Why Implicit Contract Violations Should Terminate V. Falco , V. Voutilainen
Intent
Inform
Abstract
For a detected core-language violation, the terminating response - invoke the handler, then terminate - is the default the evidence supports.
› P4318R0 Transient Benefit, Perpetual Cost: Implicit Core-Language Assertions V. Falco
Intent
Inform
Abstract
Standardizing a continuing (log-and-continue) response for implicit contract assertions on core-language undefined behavior, as a portable guarantee every implementation carries, returns less than it costs.
