Feature/any write stream readiness - #394
Conversation
…eady Construct the concrete awaitable in the wrapper's await_ready and forward its readiness, matching any_read_stream. A stream whose awaitable reports ready now completes the erased write without suspending the coroutine, which is the behavior the class docs already promised. An empty write still never touches the underlying stream, and pending streams suspend through await_suspend as before. Claude-Session: https://claude.ai/code/session_01F1KRdVbs1AubbqDNX3KkwD
The erased read wrapper has constructed the concrete awaitable in await_ready and forwarded its readiness since the beginning, but no test asserted it: every shared mock reports not-ready, so reverting to suspend-first would have passed the suite. Mirror the write-side readiness test so both wrappers' suspension skip is pinned. Claude-Session: https://claude.ai/code/session_01F1KRdVbs1AubbqDNX3KkwD
|
An automated preview of the documentation is available at https://394.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-31 13:08:25 UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #394 +/- ##
===========================================
- Coverage 98.09% 98.09% -0.01%
===========================================
Files 130 130
Lines 6291 6289 -2
===========================================
- Hits 6171 6169 -2
Misses 120 120
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 3 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
GCOVR code coverage report https://394.capy.prtest3.cppalliance.org/gcovr/index.html Build time: 2026-08-31 13:23:32 UTC |
2 participants
No description provided.