› P2583R4 Info: Symmetric Transfer and Sender Composition M. Gill , V. Falco
› P4007R3 Info: Open Issues in `std::execution::task` V. Falco , M. Gill
Intent
Info
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 C
› P4014R2 Info: The Sender Sub-Language For Beginners V. Falco , M. Gill
Intent
Info
Abstract
Every sender algorithm in C++26 - all thirty - explained, demonstrated, and mapped to its plain-C++ equivalent.
› P4035R1 Info: The Need for Escape Hatches V. Falco
Intent
Info
Abstract
C++ should make the safe thing easy, and the unsafe thing possible.
› P4036R0 Info: Why Span Is Not Enough V. Falco
Intent
Info
Abstract
C++ has bytes. A contiguous region of bytes needs a type. A sequence of such regions needs another. This paper examines the types that predictably come to mind, and their consequences.
› P4041R0 Info: Is `std::execution` a Universal Async Model? V. Falco
Intent
Info
Abstract
C++20 standardized coroutines. C++26 adds `std::execution`. Both are asynchronous models. The question is whether the
› P4046R0 Info: SAGE: Saving All Gathered Expertise V. Falco
Intent
Info
Abstract
We interviewed five experts, had AI distill their wisdom into 11 principles, built a scoring rubric, and graded our own paper first.
› P4047R0 Info: CRYSTAL BALL: Checking Predictions Against the Record V. Falco
Intent
Info
Abstract
This paper collects dated, public, falsifiable predictions about `std::execution` from proponents and critics alike, and checks each against the record.
› P4048R0 Info: Networking for C++29: A Call to Action V. Falco
› P4088R1 Info: What C++20 Coroutines Already Buy The Standard V. Falco
Intent
Info
Abstract
C++ already got an asynchronous model: regular C++20 coroutines.
› P4089R1 Info: On the Diversity of Coroutine Task Types V. Falco
Intent
Info
Abstract
The Environment parameter in `std::execution::task` makes cross-library coroutine interoperability structurally impossible without knowing every query by name.
› P4090R1 Info: Sender I/O: A Constructed Comparison V. Falco
Intent
Info
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.
› P4091R1 Info: Error Models of Regular C++ and the Sender Sub-Language V. Falco
Intent
Info
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.
› P4092R1 Info: Consuming Senders from Coroutine-Native Code V. Falco , S. Gerbino
Intent
Info
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.
› P4093R1 Info: Producing Senders from Coroutine-Native Code V. Falco , S. Gerbino
Intent
Info
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.
› P4094R1 Info: The Unification of Executors and P0443 V. Falco
Intent
Info
Abstract
The unification of three working executor models had unanticipated downstream consequences.
› P4095R1 Info: The Basis Operation and P1525 V. Falco
Intent
Info
Abstract
Of the four deficiencies that [P1525R0](https://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.
› P4096R1 Info: Coroutine Executors and P2464R0 V. Falco
Intent
Info
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.
› P4097R1 Info: The Networking Claim and P2453R0 V. Falco
Intent
Info
Abstract
The committee expressed consensus that sender/receiver is a good basis for networking. The published evidence behind that word is documented here.
› P4098R1 Info: Async Claims and Evidence V. Falco
Intent
Info
Abstract
Published claims about executors, networking, and unification shaped a decade of committee decisions. The published evidence behind those claims is documented here.
› P4099R1 Info: The Twenty-One Year Networking Arc V. Falco
Intent
Info
Abstract
Four decisions, each locally reasonable, each under-evidenced, produced a decade without networking in the C++ standard.
› P4100R1 Info: Coroutine-Native I/O for C++29 (The Network Endeavor) V. Falco , S. Gerbino , M. Vandeberg , M. Gill , M. Nejati
Intent
Info
Abstract
C++ coroutines have five language mechanisms that combine into the ideal substrate for coroutine-native I/O.
› P4123R0 Info: The Cost of Senders for Coroutine I/O V. Falco
Intent
Info
Abstract
Every concession granted. The gap remains. I/O users pay for what they do not need.
› P4124R0 Info: Combinators and Compound Results from I/O V. Falco
Intent
Info
Abstract
`std::execution::when_all` dispatches on channels. I/O errors arrive on the value channel. The combinator does not see them.
› P4126R1 Info: A Universal Continuation Model V. Falco , K. Morgenstern
Intent
Info
Abstract
Senders pay a frame allocation to enter the awaitable protocol. They do not have to.
› P4127R0 Info: The Coroutine Frame Allocator Timing Problem V. Falco
Intent
Info
Abstract
The coroutine frame allocator must arrive before the coroutine frame exists. Exactly two mechanisms can deliver it.
› P4166R0 Info: Benefits of Frame-Visible Coroutines for Senders V. Falco
Intent
Info
Abstract
Frame-visible coroutines would eliminate `std::execution::task`'s heap allocation and give sender-based coroutine algorithms full optimizer visibility.
› P4170R0 Info: A Reader's Guide to the May 2026 Mailing V. Falco
Intent
Info
Abstract
Thirty-four papers audit two decades of async decisions, deploy coroutine-native I/O at a derivatives exchange with zero per-operation allocations, bridge the result to std::execution, and deliver open-source AI evaluation tools for WG21 proposals.
› P4172R1 Info: IoAwaitable for Coroutine-Native Byte-Oriented I/O V. Falco , S. Gerbino
Intent
Info
Abstract
This paper documents the design rationale for the *IoAwaitable* protocol.
› P4178R0 Info: Trade-offs in Asynchronous Abstraction Design V. Falco
Intent
Info
Abstract
Sections of P2300R10 are compared to other sections of P2300R10 and entered into the historical record.
› P4207R0 Info: Prosecute Your Paper To Improve It V. Falco
Intent
Info
Abstract
For less than a dollar, every paper in the mailing can know its own weaknesses before the committee does.
› P4208R0 Info: C++ Contracts on Trial - Does P2900 Survive Cross-Examination? V. Falco
Intent
Info
Abstract
An AI examines [P2900R14](https://wg21.link/p2900r14) "Contracts for C++" by applying the Advocatus Diaboli from [P4207R0](https://isocpp.org/files/papers/P4207R0.pdf) "Prosecute Your Paper To
