On Thursday, June 25th, 2026 at 6:06 PM, Ruben Perez via Boost <boost@lists.boost.org> wrote:
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?
This is true. It should not work with capy::thread_pool. Something like tcp_acceptor does need the reactor. The Boost.Asio integration is outside of the scope of the Capy/Corosio review (it is not in develop or master). It is incomplete work.