|
| 1 | +# Paper Folio |
| 2 | + |
| 3 | +Prescriptions for fixing WG21 |
| 4 | +- [P4134R0](https://isocpp.org/files/papers/P4134R0.pdf) - A Better WG21 |
| 5 | + |
| 6 | +A plan for networking in C++29 |
| 7 | +- [P4100R0](https://isocpp.org/files/papers/P4100R0.pdf) - The Network Endeavor: Coroutine-Native I/O for C++29 |
| 8 | + |
| 9 | +The solution to the political problem of coroutine I/O |
| 10 | +- [P4126R0](https://isocpp.org/files/papers/P4126R0.pdf) - A Universal Continuation Model |
| 11 | + |
| 12 | +This shows the cost of making senders the base of I/O operations |
| 13 | +- [P4123R0](https://isocpp.org/files/papers/P4123R0.pdf) - The Cost of Senders for Coroutine I/O |
| 14 | + |
| 15 | +How WG21 can work together to deliver a big feature: networking |
| 16 | +- [P4048R0](https://isocpp.org/files/papers/P4048R0.pdf) - Networking for C++29: A Call to Action |
| 17 | + |
| 18 | +Why coroutines are the natural foundation of networking |
| 19 | +- [P4088R0](https://isocpp.org/files/papers/P4088R0.pdf) - The Case for Coroutines |
| 20 | + |
| 21 | +This is the narrowest abstraction which enables coroutine I/O |
| 22 | +- [D4003R1](https://isocpp.org/files/papers/P4003R1.pdf) - Coroutines for I/O |
| 23 | + |
| 24 | +These papers demonstrate working sender interoperability |
| 25 | +- [P4092R0](https://isocpp.org/files/papers/P4092R0.pdf) - Consuming Senders from Coroutine-Native Code |
| 26 | +- [P4093R0](https://isocpp.org/files/papers/P4093R0.pdf) - Producing Senders from Coroutine-Native Code |
| 27 | + |
| 28 | +Supporting evidence for A Better WG21 |
| 29 | +- [P4129R0](https://isocpp.org/files/papers/P4129R0.pdf) - The Dynamics of Voting in WG21 |
| 30 | +- [P4130R0](https://isocpp.org/files/papers/P4130R0.pdf) - The Convenership's Structural Influence Over WG21 |
| 31 | +- [P4131R0](https://isocpp.org/files/papers/P4131R0.pdf) - Retrospective: Effects of the WG21 Train Model |
| 32 | +- [P4133R0](https://isocpp.org/files/papers/P4133R0.pdf) - What Every Proposal Must Contain |
| 33 | + |
| 34 | +Technical analysis of presented problems and solutions |
| 35 | + |
| 36 | +- [P2583R3](https://isocpp.org/files/papers/P2583R3.pdf) - Symmetric Transfer and Sender Composition |
| 37 | +- [D4007R1](https://isocpp.org/files/papers/P4007R1.pdf) - Open Issues in `std::execution::task` |
| 38 | +- [D4014R1](https://isocpp.org/files/papers/P4014R1.pdf) - The Sender Sub-Language |
| 39 | +- [P4036R0](https://isocpp.org/files/papers/P4036R0.pdf) - Why Span Is Not Enough |
| 40 | +- [P4035R0](https://isocpp.org/files/papers/P4035R0.pdf) - The Need for Escape Hatches |
| 41 | +- [P4089R0](https://isocpp.org/files/papers/P4089R0.pdf) - On the Diversity of Coroutine Task Types |
| 42 | +- [P4090R0](https://isocpp.org/files/papers/P4090R0.pdf) - Sender I/O: A Constructed Comparison |
| 43 | +- [P4091R0](https://isocpp.org/files/papers/P4091R0.pdf) - Error Models of Regular C++ and the Sender Sub-Language |
| 44 | +- [P4124R0](https://isocpp.org/files/papers/P4124R0.pdf) - Combinators and Compound Results from I/O |
| 45 | +- [P4127R0](https://isocpp.org/files/papers/P4127R0.pdf) - The Coroutine Frame Allocator Timing Problem |
| 46 | + |
| 47 | +This summarizes the failure modes evidenced by the networking retrospective |
| 48 | +- [P4050R0](https://isocpp.org/files/papers/P4050R0.pdf) - Failure Modes in Large-Scale Standardization |
| 49 | + |
| 50 | +This is the retrospective supporting evidence for P4050 |
| 51 | +- [P4094R0](https://isocpp.org/files/papers/P4094R0.pdf) - Retrospective: The Unification of Executors and P0443 |
| 52 | +- [P4095R0](https://isocpp.org/files/papers/P4095R0.pdf) - Retrospective: The Basis Operation and P1525 |
| 53 | +- [P4096R0](https://isocpp.org/files/papers/P4096R0.pdf) - Retrospective: Coroutine Executors and P2464R0 |
| 54 | +- [P4097R0](https://isocpp.org/files/papers/P4097R0.pdf) - Retrospective: The Networking Claim and P2453R0 |
| 55 | +- [P4098R0](https://isocpp.org/files/papers/P4098R0.pdf) - Retrospective: Async Claims and Evidence |
| 56 | +- [P4099R0](https://isocpp.org/files/papers/P4099R0.pdf) - Twenty-One Years: The Arc of Networking in C++ |
| 57 | + |
| 58 | +This is a fun paper about how to canvass the Profiles feature |
| 59 | +- [P4137R0](https://isocpp.org/files/papers/P4137R0.pdf) - PAVE: Profile Analysis and Verification Evidence |
0 commit comments