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

Select	Paper	Title	Authors	Audience
	P3373R4	Of Operation States and Their Lifetimes	R. Leahy	WG21
Intent Proposal Mailing Date 2026-04 Post-Croydon Author(s) Robert Leahy Target Audience WG21 Revisions R3 R2 Tracking issue View on GitHub Disposition Date 2026-03Adopted Abstract In broad terms a regular (i.e. synchronous) function call has access to two forms of storage throughout its lifetime (note that the “lifetime” of a regular function call is the time between the call thereto and the return therefrom):
	P3986R1	A Wording Strategy for Inlinable Receivers	R. Leahy	LWG
Intent Proposal Mailing Date 2026-04 Post-Croydon Author(s) Robert Leahy Target Audience LWG Revisions R0 Tracking issue View on GitHub Disposition Date 2026-03Adopted Abstract When a sender and receiver are connected the result is an operation state. That operation state, once started, is the locus of an asynchronous operation which, upon completion, must notify its consumer of said completion (§33.3 [exec.async.ops]). The way this notification is accomplished is by sending a completion signal to the receiver provided when connecting the sender and receiver.
	P4151R1	Rename affine_on	R. Leahy	LEWG
Intent Proposal Mailing Date 2026-04 Post-Croydon Author(s) Robert Leahy Target Audience LEWG Revisions R0 Tracking issue View on GitHub Disposition Date 2026-03Adopted Abstract When `std::execution::affine_on` was added [1] it was a binary-invocable object accepting two parameters, respectively:
	P4191R0	is_nothrow_connectable_in	R. Leahy	LEWG SG1
Intent Proposal Mailing Date 2026-04 Post-Croydon Author(s) Robert Leahy Target Audience LEWG SG1 Tracking issue View on GitHub Abstract Under the original design of `std::execution` [1] one could check whether or not `std::execution::connect` threw an exception via:

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

Mailings Beta

Sign in