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

	Paper	Title	Authors	Audience
	P3950R1	return_value & return_void Are Not Mutually Exclusive	R. Leahy	CWG
Mailing Date 2026-07 Post-Brno Author(s) Robert Leahy Target Audience CWG Revisions R0 Tracking issue View on GitHub Disposition Date 2026-06 Abstract The standard specifies the effect of `co_return` statements in terms of equivalent statements within the context of a replacement body (§9.6.4 [dcl.fct.def.coroutine]). Like a regular `return` statement `co_return` statements have two distinct forms: Those that return `void` and those that return some value. These are specified as follows (§8.8.5 [stmt.return.coroutine]):
	P4217R1	when_all() is just just()	R. Leahy	LEWG
Mailing Date 2026-07 Post-Brno Author(s) Robert Leahy Target Audience LEWG Revisions R0 Tracking issue View on GitHub Abstract The standard currently specifies, by fiat, that `std::execution::when_all()` is ill-formed (§33.9.12.12 [exec.when.all]):
	P4254R0	Throwing Violation Handlers Are Post Hoc Library Design	R. Leahy	LEWG
Mailing Date 2026-07 Post-Brno Author(s) Robert Leahy Target Audience LEWG Tracking issue View on GitHub Abstract The Lakos Rule [1] has long been treated as a trump card in LEWG: A proposal contains a function with a precondition which is declared `noexcept`, someone in the room invokes “the Lakos Rule,” and the function must presumptively be redesigned to remove the `noexcept`. This has impeded the adoption of `noexcept` in the library, and has led to arguably-ridiculous consequences (e.g. `std::vector::ope
	P4269R0	when_all Oughtn't Hallucinate set_stopped	R. Leahy	LEWG SG1
Mailing Date 2026-07 Post-Brno Author(s) Robert Leahy Target Audience LEWG SG1 Tracking issue View on GitHub Abstract When `std::execution::when_all` is provided with multiple senders it becomes possible that:
	P4282R0	Away From co_yield For std::execution::task	R. Leahy	LEWG SG1
Mailing Date 2026-07 Post-Brno Author(s) Robert Leahy Target Audience LEWG SG1 Tracking issue View on GitHub Abstract The coroutine promise protocol shipped in C++20 not only banned `return_void` and `return_value` on the same promise type, but did so in an unusually restrictive manner [1]. Notably the aforementioned manner barred implementing the aforementioned mutual exclusion via mutually exclusive constraints.
	P4288R0	Stop the Decay	R. Leahy	LEWG SG1
Mailing Date 2026-07 Post-Brno Author(s) Robert Leahy Target Audience LEWG SG1 Tracking issue View on GitHub Abstract `std::execution` can be thought of as the realization of the asynchronous analogue of a synchronous function [1][2]. The sender is the function itself (with all arguments selected and applied), the receiver is the channel by which the function communicates with its caller (in the synchronous realm by returning or throwing), and the operation state is the “stack” (i.e. a collection of variables wit
	P4293R0	std::execution::decay_copy	R. Leahy	LEWG SG1
Mailing Date 2026-07 Post-Brno Author(s) Robert Leahy Target Audience LEWG SG1 Tracking issue View on GitHub Abstract * Allows for asynchronous operations which advertise ref-qualified completions, and
	P4320R0	std::execution::sequence	R. Leahy	LEWG SG1
Mailing Date 2026-07 Post-Brno Author(s) Robert Leahy Target Audience LEWG SG1 Tracking issue View on GitHub Abstract `sequence` adapts any number of input senders into a sender which completes when all input senders have completed, with each input sender’s asynchronous operation being started only after the completion of the preceding input sender’s asynchronous operation.

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

Mailings Beta

Sign in