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

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

2026 Aug · 1 of 6

Pick months in 2026

Filters SG1 Clear all
4 out of 4 papers selected for export
SelectPaper Title Authors Audience Doc Date
P3955R1 It's Scopes All the Way Down R. Leahy 2026-08-10
Doc Date 2026-08-10
Mailing Date 2026-08 Unassigned
Author(s) Robert Leahy
Target Audience LEWGSG1
Revisions R0
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.
P4282R1 Away From co_yield For std::execution::task R. Leahy 2026-08-02
Doc Date 2026-08-02
Mailing Date 2026-08 Unassigned
Author(s) Robert Leahy
Target Audience LEWGSG1
Revisions R0
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.
P4288R1 Stop the Decay R. Leahy 2026-07-31
Doc Date 2026-07-31
Mailing Date 2026-08 Unassigned
Author(s) Robert Leahy
Target Audience LEWGSG1
Revisions R0
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
P4329R0 variant_sender R. Leahy 2026-07-29
Doc Date 2026-07-29
Mailing Date 2026-08 Unassigned
Author(s) Robert Leahy
Target Audience LEWGSG1
Abstract Under the status quo of the C++29 working draft one can write asynchronous code which branches synchronously:
Showing 4 of 4 papers · source: open-std.org