Add constraints to IoAwaitable - #383
Conversation
This add constraints to IoAwaitabe, so that the concept reflects what is needed for a type to be used in Capy-coroutines: * `await_ready`, * `await_resume`, * move construction.
|
This addresses #356. |
|
An automated preview of the documentation is available at https://383.capy.prtest3.cppalliance.org/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-08-23 23:43:19 UTC |
|
GCOVR code coverage report https://383.capy.prtest3.cppalliance.org/gcovr/index.html Build time: 2026-08-23 23:56:36 UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #383 +/- ##
========================================
Coverage 98.09% 98.09%
========================================
Files 130 130
Lines 6291 6291
========================================
Hits 6171 6171
Misses 120 120
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:
|
|
Typo in "funciton" Should it be convertible to bool instead of The return value excludes typed handles (e.g. The Doxygen comment example drops the old semantic-requirements list about stop tokens and frame allocator propagation. Consider restoring this guidance in some form. |
Fixed.
C++ awaiters are not allowed to return "convertible to
My bad. I changed the concept to allow this.
They seem not to apply to the awaitable, but rather to the bodies of the resumed coroutines. Maybe instead, I will mention this in a (new) chapter which explains how to define your own coroutine? |
This add constraints to IoAwaitabe, so that the concept reflects what is needed for a type to be used in Capy-coroutines:
await_ready,await_resume,