io_result can be co_yielded in io_task

[klemens-morgenstern]

No description provided.

[cppalliance-bot]

An automated preview of the documentation is available at https://301.capy.prtest3.cppalliance.org/index.html

If more commits are pushed to the pull request, the docs will rebuild at the same URL.

2026-06-04 15:16:57 UTC

[cppalliance-bot]

GCOVR code coverage report https://301.capy.prtest3.cppalliance.org/gcovr/index.html
LCOV code coverage report https://301.capy.prtest3.cppalliance.org/genhtml/index.html
Coverage Diff Report https://301.capy.prtest3.cppalliance.org/diff-report/index.html

Build time: 2026-06-04 15:34:56 UTC

[klemens-morgenstern]

The Idea was rejected by vinnie.

Vinnie  [2:05 AM] I don't like it
Vinnie  [2:06 AM] In principle I like making things more ergonomic, so it is an interesting idea. But it turns co_yield into a different idiom. And it also supports std::execution::task 's decision to return using co_yield, which I don't like.