Repository navigation
docs: add a Why Not std::execution design page - #456
mvandeberg wants to merge 1 commit into
Conversation
Give the std::execution comparison its own page beside the Asio, Cobalt and TooManyCooks comparisons. The page contrasts the two models' context direction, frame-allocation timing, scheduling primitives and stop-token handling, lists what Capy gives up, and links both sender bridges and the BOOST1001 comparison paper. The context-direction and frame-allocation-timing argument was repeated in the Executor, Run API and Why Not Asio pages. Each now keeps its topic-specific point and links to the new page. The sender bridge example and the ContextAwaitable tutorial link to it as well. Why Not Asio also now describes std::execution and P3552 task as in the C++26 working draft, and no longer claims the frame allocator can't be a parameter. Closes cppalliance#403
|
An automated preview of the documentation is available at https://456.capy.prtest3.cppalliance.org/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-10-17 15:49:12 UTC |
|
GCOVR code coverage report https://456.capy.prtest3.cppalliance.org/gcovr/index.html Build time: 2026-10-17 16:02:15 UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #456 +/- ##
========================================
Coverage 98.43% 98.43%
========================================
Files 137 137
Lines 7297 7297
========================================
Hits 7183 7183
Misses 114 114
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
This branch has not been deployed
2 participants
Give the std::execution comparison its own page beside the Asio, Cobalt and TooManyCooks comparisons. The page contrasts the two models' context direction, frame-allocation timing, scheduling primitives and stop-token handling, lists what Capy gives up, and links both sender bridges and the BOOST1001 comparison paper.
The context-direction and frame-allocation-timing argument was repeated in the Executor, Run API and Why Not Asio pages. Each now keeps its topic-specific point and links to the new page. The sender bridge example and the ContextAwaitable tutorial link to it as well. Why Not Asio also now describes std::execution and P3552 task as in the C++26 working draft, and no longer claims the frame allocator can't be a parameter.
Closes #403