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
Evolution
Study Groups
Mailings
1 · Year 1 · Month

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

2026 Jan · 1 of 6

Pick months in 2026

Add Year +

Select Years To Display

Current Years Selected

2026
Filters Author: Robert Leahy Clear all
3 out of 3 papers selected for export
SelectPaper Title Authors Audience Doc Date
P3373R2 Of Operation States and Their Lifetimes R. Leahy
Intent Proposal
Mailing Date 2026-01 Unassigned
Author(s) Robert Leahy
Target Audience LEWG
Revisions R4R3
Tracking issue View on GitHub
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):
P3950R0 return_value & return_void Are Not Mutually Exclusive R. Leahy
Intent Proposal
Mailing Date 2026-01 Unassigned
Author(s) Robert Leahy
Target Audience EWGSG1SG17
Revisions R1
Tracking issue View on GitHub
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]):
P3955R0 It's Scopes All the Way Down R. Leahy
Intent Proposal
Mailing Date 2026-01 Unassigned
Author(s) Robert Leahy
Target Audience LEWGSG1
Revisions R1
Tracking issue View on GitHub
Abstract The fundamental scope algorithm is `within`. It establishes a scope by running an enter scope sender. Thereafter it allows a child operation to run (in that scope since the exit scope sender has not yet run), and then before completing the overall operation runs the exit scope sender yielded by the enter scope sender.
Showing 3 of 3 papers · source: open-std.org