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.

Submit Issue C++ Standards Committee Papers

Disposition Updated

1 · Year 1 · Month

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

Add Year +

Select Years To Display

Current Years Selected

2026 2025

Group by date?

Select	Paper	Title	Authors	Audience	Doc Date	Mailing Date
	P3223R2	Making std::istream::ignore less surprising	Jonathan Wakely J. Wakely	LWG	2025-06-20	2025-07
Doc Date 2025-06-20 Mailing Date 2025-07 Post-Sofia Author(s) Jonathan Wakely Target Audience LWG Tracking issue View on GitHub Disposition Date 2025-06Adopted Abstract `std::istream::ignore(n, delim)` has surprising behaviour if `delim` is a `char` with a negative value. We can remove the surprise and make code more robust.
	P3348R4	C++26 should refer to C23 not C17	Jonathan Wakely J. Wakely	LWG SG6	2025-06-19	2025-07
Doc Date 2025-06-19 Mailing Date 2025-07 Post-Sofia Author(s) Jonathan Wakely Target Audience LWG SG6 Tracking issue View on GitHub Disposition Date 2025-06Adopted Abstract There is a new version of the ISO C standard, so we should update our normative reference, and update the header synopses in the library clauses to match the content of the C standard library. A similar change to rebase C++17 on C11 was previously done via [P0063R3: C++17 should refer to C11 instead of C99](https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0063r3.html) (see R0 for more det
	P3503R3	Make type-erased allocator use in promise and packaged_task consistent	Nicolas Morales N. Morales , Jonathan Wakely J. Wakely	LWG	2025-06-19	2025-07
Doc Date 2025-06-19 Mailing Date 2025-07 Post-Sofia Author(s) Nicolas Morales, Jonathan Wakely Target Audience LWG Tracking issue View on GitHub Disposition Date 2025-06Adopted Abstract [[LWG2095](https://wg21.link/lwg2095)] points out inconsistencies in the API of `std::promise`; namely that `uses_allocator<promise<R>, A>::value` is specified to be true in 32.10.6 [[futures.promise]](https://wg21.link/futures.promise), yet is missing the appropriate constructor taking an rvalue of promise.

Showing 3 of 3 papers · source: open-std.org

Mailings Beta

Sign in