25 Jun
2026
25 Jun
'26
4:05 p.m.
Which makes me think that Corosio can only be used with corosio::io_context, and no other execution contexts.
That is correct, for now. The Boost.Asio compatibility is not part of Capy *yet*. It is un-reviewed and not merged. To support this we simply lazily load services.
If I'm reading Corosio's code correctly, it is not enough to construct the services, but you also need to run the scheduler. This happens in io_context::run(). How would this work for capy::thread_pool or the Asio integration case?