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

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

2026 Jul · 1 of 5

Pick months in 2026

Filters Author: Robert Leahy SG1 Clear all
5 out of 5 papers selected for export
Paper Title Authors Audience Doc Date Audit
P4269R0 when_all Oughtn't Hallucinate set_stopped R. Leahy
Mailing Date 2026-07 Post-Brno
Author(s) Robert Leahy
Target Audience LEWGSG1
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
Mailing Date 2026-07 Post-Brno
Author(s) Robert Leahy
Target Audience LEWGSG1
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
Mailing Date 2026-07 Post-Brno
Author(s) Robert Leahy
Target Audience LEWGSG1
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
Mailing Date 2026-07 Post-Brno
Author(s) Robert Leahy
Target Audience LEWGSG1
Tracking issue View on GitHub
Abstract * Allows for asynchronous operations which advertise ref-qualified completions, and
P4320R0 std::execution::sequence R. Leahy
Mailing Date 2026-07 Post-Brno
Author(s) Robert Leahy
Target Audience LEWGSG1
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 5 of 5 papers · source: open-std.org