› P2583R3 Info: Symmetric Transfer and Sender Composition
Mungo Gill
M. Gill
,
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
C++20 provides symmetric transfer ([P0913R1](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0913r1.html)[1]) - a mechanism where `await_suspend` returns a `coroutine_handle<>` and the compiler resumes the designated coroutine as a tail call. Coroutine chains execute in constant stack space. `std::execution`
› P4003R2 Ask: A Minimal Coroutine Execution Model
Vinnie Falco
V. Falco
,
Mungo Gill
M. Gill
,
Steve Gerbino
S. Gerbino
2026-04
Intent
Proposal
Abstract
This paper asks the committee to advance the *IoAwaitable* protocol as a standard coroutine execution model.
› P4007R2 Info: Open Issues in `std::execution::task`
Vinnie Falco
V. Falco
,
Mungo Gill
M. Gill
2026-04
Intent
Informational
Abstract
`std::execution::task` ([P3552R3](https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p3552r3.html)[1]) had open issues identified by national ballot comments, LWG issues, and published papers. Croydon resolved several. This paper classifies each issue by whether it can be resolved after C++26 ships or whether shipping forecloses the fix, and notes which classified issues were addressed at Cr
› P4014R1 Info: The Sender Sub-Language For Beginners
Vinnie Falco
V. Falco
,
Mungo Gill
M. Gill
2026-04
Intent
Informational
Abstract
Every sender algorithm in C++26 - all thirty - explained, demonstrated, and mapped to its plain-C++ equivalent.
› P4035R0 Info: The Need for Escape Hatches
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
C++ should make the safe thing easy, and the unsafe thing possible.
› P4088R0 Info: What C++20 Coroutines Already Buy The Standard
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
C++ already got an asynchronous model: regular C++20 coroutines.
› P4089R0 Info: On the Diversity of Coroutine Task Types
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
The Environment parameter in `std::execution::task` makes cross-library coroutine interoperability structurally impossible without knowing every query by name.
› P4090R0 Info: Sender I/O: A Constructed Comparison
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
The sender composition algebra does not apply to compound I/O results without losing data, and the construction that preserves all data produces code identical to the coroutine version.
› P4091R0 Info: Error Models of Regular C++ and the Sender Sub-Language
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
Both coroutines and senders destroy compound data at an abstraction floor - the difference is that the sender floor sits below the composition algebra, and the coroutine floor is opt-in.
› P4092R0 Info: Consuming Senders from Coroutine-Native Code
Vinnie Falco
V. Falco
,
Steve Gerbino
S. Gerbino
2026-04
Intent
Informational
Abstract
A single class template bridges sender-based code into coroutine-native I/O with inline operation state, correct stop propagation, and automatic dispatch-back.
› P4093R0 Info: Producing Senders from Coroutine-Native Code
Vinnie Falco
V. Falco
,
Steve Gerbino
S. Gerbino
2026-04
Intent
Informational
Abstract
Coroutine-native awaitables can be wrapped as senders, but compound I/O results must be reduced to an error code before crossing the bridge.
› P4094R0 Info: The Unification of Executors and P0443
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
The unification of three working executor models had unanticipated downstream consequences.
› P4095R0 Info: The Basis Operation and P1525
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
Of the four deficiencies that [P1525R0](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1525r0.pdf)[1] identified in `execute(F&&)`, three do not arise under the original framing of the callable as a continuation, and the fourth addresses a different question.
› P4096R0 Info: Coroutine Executors and P2464R0
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
The committee set aside the Networking TS in 2021. The process had no mechanism to verify that the analysis examined every applicable framing, and no mechanism to revisit the outcome against evidence.
› P4097R0 Info: The Networking Claim and P2453R0
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
The committee expressed consensus that sender/receiver is a good basis for networking. The published evidence behind that word is documented here.
› P4098R0 Info: Async Claims and Evidence
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
Published claims about executors, networking, and unification shaped a decade of committee decisions. The published evidence behind those claims is documented here.
› P4099R0 Info: The Twenty-One Year Networking Arc
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
Four decisions, each locally reasonable, each under-evidenced, produced a decade without networking in the C++ standard.
› P4100R0 Info: Coroutine-Native I/O for C++29 (The Network Endeavor)
Vinnie Falco
V. Falco
,
Steve Gerbino
S. Gerbino
,
Michael Vandeberg
M. Vandeberg
,
Mungo Gill
M. Gill
,
Mohammad Nejati
M. Nejati
2026-04
Intent
Informational
Abstract
C++ coroutines have five language mechanisms that combine into the ideal substrate for coroutine-native I/O.
› P4126R0 Info: A Universal Continuation Model
Vinnie Falco
V. Falco
,
Klemens Morgenstern
K. Morgenstern
2026-04
Intent
Informational
Abstract
Senders pay a frame allocation to enter the awaitable protocol. They do not have to.
› P4137R0 Info: Profile Analysis and Verification Evidence (PAVE)
Vinnie Falco
V. Falco
2026-04
Intent
Informational
Abstract
The paper offers a way to measure what the type-safety profile actually covers.
› P4172R0 Info: IoAwaitable for Coroutine-Native Byte-Oriented I/O
Vinnie Falco
V. Falco
,
Steve Gerbino
S. Gerbino
2026-04
Intent
Informational
Abstract
This paper documents the design rationale for the *IoAwaitable* protocol.
