[RFC] Add initial C++20 coroutine support #653
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The initial C++20 coroutine support. I may implement C++26 sender receiver support later, once I fully grasped its design (ref: stdexec).
The async version of the socket is placed under
zmq::async::corral
. It's implemented for corral but any open coroutine implementation canco_await
on thesend
/recv
operations. Boost.Cobalt is another open coroutine implementation.Issues:
io_context
in parallel. M:N multiplexing isn't possible currently with corral (Note that C++26 sender receiver does have proper M:N multiplexing)Alternatively wait for my implementation for sender receiver support (again, once I've grasped it myself), which should resolve 3 and 5.
Also refer to #400