WG21 PAPERS

Mailings Beta

Volunteer-driven · Not affiliated with WG21 or ISO

Filter and export papers from the C++ Committee’s monthly mailings by time frame and audience using the options below, or refine your export further with the Select button. Links point directly to the official WG21 papers on open-std.org.

Audience
General
Wording
Evolution
Study Groups
Mailings
1 · Year 1 · Month

Select the arrow to the right of the year to filter for specific months.

2026 Sep · 1 of 7

Pick months in 2026

Add Year +

Select Years To Display

Current Years Selected

2026
Filters LWG Clear all
8 out of 8 papers selected for export
SelectPaper Title Authors Audience Doc Date Mailing Date
P3211R3 views::transform_join H. Kang 2026-09-09 2026-09
Doc Date 2026-09-09
Mailing Date 2026-09 Unassigned
Author(s) Hewill Kang
Target Audience LEWGLWGSG9
Revisions R2
Tracking issue View on GitHub
Abstract We propose `views::transform_join`, a range adaptor that applies a function returning a range for each element, then flattens the result. This pattern, commonly known as *flat mapping*, is widespread in functional programming and data processing. Providing it as a dedicated view improves readability and expressiveness, and also opens opportunities for optimization in lazy evaluation contexts.
P3255R3 Expose whether atomic notifying operations are lock-free B. Bi 2026-09-03 2026-09
Doc Date 2026-09-03
Mailing Date 2026-09 Unassigned
Author(s) Brian Bi
Target Audience LWG
Tracking issue View on GitHub
Abstract The atomic notifying functions for `std::atomic_flag` are not always lock-free even though `std::atomic_flag` is specified to always be lock-free. Therefore, use of `std::atomic_flag::notify_one` or `std::atomic_flag::notify_all` may cause unpredictable behavior when called in a signal handler, even though the Standard currently claims that these functions are signal-safe. It would be useful for s
P3427R9 Hazard Pointer Synchronous Reclamation M. Michael, M. Wong, P. McKenney, M. Wever 2026-09-04 2026-09
Doc Date 2026-09-04
Mailing Date 2026-09 Unassigned
Target Audience LWG
Revisions R8R7R6R5R4R3
Tracking issue View on GitHub
Abstract This paper proposes extending the C++26 hazard pointer interface to support synchronous reclamation. This revision, P3427R9, revises R8 by following LWG 2026-08-21 feedback. R9 was reviewed by LWG on 2026-09-04 and voted for inclusion in C++29.
P3642R7 Carry-less product: std::clmul J. Schultke 2026-09-21 2026-09
Doc Date 2026-09-21
Mailing Date 2026-09 Unassigned
Author(s) Jan Schultke
Target Audience LWG
Revisions R6R5R4
Tracking issue View on GitHub
Abstract Add widening and non-widening carry-less multiplication functions.
P3928R2 static_sized_range H. Kang 2026-08-26 2026-09
Doc Date 2026-08-26
Mailing Date 2026-09 Unassigned
Author(s) Hewill Kang
Target Audience LEWGLWGSG9
Revisions R1
Tracking issue View on GitHub
Abstract This paper introduces `static_sized_range`, a refinement of `sized_range` for ranges whose sizes are known at compile time.
P4230R1 Implementability of P0943's C++ stdatomic.h H. Boehm 2026-08-15 2026-09
Doc Date 2026-08-15
Mailing Date 2026-09 Unassigned
Author(s) Hans Boehm
Target Audience LEWGLWGSG1SG22
Revisions R0
Tracking issue View on GitHub
Abstract [P0943](http://wg21.link/p0943) was accepted into C++23. One of the national body comments for C++26 proposed its removal. SG1 voted without objection to retain it. LEWG almost obtained consensus to remove it. This is an attempt to outline the issues, as mostly exposed in the LEWG discussion, a later reflector discussion (“stdatomic.h in C++”, starting March 27, 2026), and some [discussion on a](h
P4354R0 No More transform_sender Workarounds R. Leahy 2026-09-01 2026-09
Doc Date 2026-09-01
Mailing Date 2026-09 Unassigned
Author(s) Robert Leahy
Target Audience LWG
Abstract This paper proposes wording-only changes to simplify the specification of `let_value`, `let_error`, and `let_stopped`, along with future, proposed asynchronous algorithms.
P4378R0 Align exact-width integer types with C M. Çağrı 2026-09-22 2026-09
Doc Date 2026-09-22
Mailing Date 2026-09 Unassigned
Author(s) Murat Can Çağrı
Target Audience LEWGLWGSG22
Abstract C23 requires the exact-width typedef names for every width for which an implementation provides a standard or extended integer type with no padding bits. C++ retains this requirement only for widths 8, 16, 32, and 64. This paper aligns C++ with C23.
Showing 8 of 8 papers · source: open-std.org