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
	P3008R6	Atomic floating-point min/max	Gonzalo Brito Gadeschi G. Gadeschi , David Sankel D. Sankel	LWG	2025-06-19	2025-07
Doc Date 2025-06-19 Mailing Date 2025-07 Post-Sofia Author(s) Gonzalo Brito Gadeschi, David Sankel Target Audience LWG Tracking issue View on GitHub Disposition Date 2025-06Adopted Abstract [P0493R4](https://wg21.link/P0493R4) Atomic minimum/maximum proposes the addition of `atomic<T>::fetch_min` and `atomic<T>::fetch_max` operations, which atomically perform `std::min` and `std::max` computations.
	P3111R8	Atomic Reduction Operations	Gonzalo Brito Gadeschi G. Gadeschi , Simon Cooksey S. Cooksey , Daniel Lustig D. Lustig	LWG	2025-06-19	2025-07
Doc Date 2025-06-19 Mailing Date 2025-07 Post-Sofia Author(s) Gonzalo Brito Gadeschi, Simon Cooksey, Daniel Lustig Target Audience LWG Revisions R7 Tracking issue View on GitHub Disposition Date 2025-06Adopted Abstract Concurrent algorithms performing atomic RMW operations that discard the old fetched value are very common in high-performance computing, e.g., finite-element matrix assembly, data analytics (e.g. building histograms), etc.
	P3248R4	Require [u]intptr_t	Gonzalo Brito Gadeschi G. Gadeschi	LWG	2025-06-19	2025-07
Doc Date 2025-06-19 Mailing Date 2025-07 Post-Sofia Author(s) Gonzalo Brito Gadeschi Target Audience LWG Revisions R5 Tracking issue View on GitHub Abstract Proposals like [P2835](https://wg21.link/p2835) and [P3125](https://wg21.link/P3125) use `[u]intptr_t` as an integer type capable of holding a pointer value in their APIs<sup>[1]</sup>. However, `[u]intptr_t` being optional forces sub-optimal design choices such as making APIs optional or introducing workarounds.

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

Mailings Beta

Sign in