WG21/P2300

P2300 std::execution

• https://github.com/cplusplus/papers/issues/1054
• P2403R0 Presentation on P2300 - std::execution (PDF)
• P2428R0 Issues and questions with P2300 (PDF)
• P2430R0 Partial success scenarios with P2300 (PDF)
• P2431R0 Plans for P2300 Revision 2 (PDF)
• P2444R0 The Asio asynchronous model (PDF)
• P2463R0 The Asio asynchronous model - Slides for P2444r0 (PDF)
• P2469R0 Response to P2464: The Networking TS is baked, P2300 Sender/Receiver is not. (PDF)
• P2470R0 Slides for presentation of P2300R2: std::execution (sender/receiver) (PDF)
• P2471R1 NetTS, ASIO and Sender Library Design Comparison (PDF)
• P2479R0 Slides for P2464 - Senders and Receivers, Composition, for real (PDF)
• P2480R0 Response to P2471: "NetTS, Asio, and Sender library design comparison" - corrected and expanded (PDF)
• P2532R0 Removing exception_ptr from the Receiver Concepts [Approved to P2300]
• P2555R1 Naming improvements for std::execution
• P2079R3 System execution context
• P2500R0 C++17 parallel algorithms and P2300

onihusubeさん解説

• ［C++］WG21月次提案文書を眺める（2021年06月）
• ［C++］WG21月次提案文書を眺める（2021年07月）
• ［C++］WG21月次提案文書を眺める（2021年10月）
• ［C++］ ExecutorとNetworking TSで起きていたこと
• ［C++］WG21月次提案文書を眺める（2021年12月）
• ［C++］WG21月次提案文書を眺める（2022年01月）
• ［C++］WG21月次提案文書を眺める（2022年04月）
• ［C++］WG21月次提案文書を眺める（2023年02月）
• ［C++］WG21月次提案文書を眺める（2023年05月）

https://github.com/cplusplus/papers/issues/1054#issuecomment-929550039

2021-09-28 Joint Library Evolution and Concurrency Telecon

POLL: We must have a single async model for the C++ Standard Library.
Outcome: No consensus.
POLL: Knowing what we know today, we should continue considering shipping the Networking TS in C++23.
Outcome: No consensus.
POLL: Knowing what we know today, we should continue considering shipping P2300 std::execution in C++23.
Outcome: No consensus.

🤷
https://twitter.com/Cor3ntin/status/1443522194152345600

P2400R2 Library Evolution Report: 2021-06-01 to 2021-09-20, §2.2.1 Executors

Over the Summer of 2021, Library Evolution reviewed P2300R0 (std::execution), a new streamlined Executors proposal from some of the authors of P0443R14 (A Unified Executors Proposal for C++). The aim of P2300 was to simplify Executors down to a minimal core and make the proposal more accessible and easier to understand. The new proposal was well received by Library Evolution, and we had consensus that we want to proceed with P2300 instead of P0443.

However, there is still disagreement between the proponents of P2300 and the proponents of P2444R0, the async model of the Networking TS. During our discussions, we have begun to question whether we need to pursue a single unified asynchronous model for both the Networking TS and structured concurrency.

It is unclear at this point whether P2300, or any other form of Executors, will be ready for C++23. While we have consensus on the design of P2300, there are still questions about field experience and maturity. Given that the window for C++23 closes at the end of 2021, the likelihood of including Executors in C++23 is rapidly diminishing.

P2489R0 Library Evolution Plan for Completing C++23

The following is what we will work on delivering in the rest of the C++23 design cycle. This is by no means a guarantee that these facilities will make it into C++23.
We will commit significant time and resources to the following work, which has previously been identified as priorities:

P2300: std::execution

• Plenary adopted priority (see P0592).
• Library Evolution voted to continue working on this in the C++23 cycle.

https://github.com/cplusplus/papers/issues/1054#issuecomment-1012197308

2021-01-11 and 2021-01-12 Library Evolution Telecon Minutes

POLL: Produce a P2300R4 (std::execution), modified as described below, and then send the revised paper to LWG for C++23 with priority 1 (to be confirmed with a Library Evolution electronic poll).
1.Removing untyped senders from P2300

SF/WF/N/WA/SA = 15/9/1/3/6
Outcome: Weak Consensus

https://github.com/cplusplus/papers/issues/1054#issuecomment-1041721767

January electronic polling

Send [P2300R4] (std::execution) to Library Working Group for C++23, classified as a focus ([P0592R4] bucket 1 item)
SF/F/N/A/SA = 23/14/0/6/11
No consensus. There is sustained strong opposition against including such a large proposal into C++23 at such a late stage. It is also unclear whether we would be able to complete wording review in the limited time we have available. Timing is a major factor in the lack of consensus. The overall design still has strong support. The Chair, Bryce Adelstein Lelbach, asked Vice Chairs Fabio Fracassi and Ben Craig to determine consensus on this poll, as the Chair is one of the co-authors of P2300. The Chair fully supports their decision.

C++26(以降)に向けて再スケジューリング確定。

What are Senders Good For, Anyway?, Eric Niebler, 2024/2