Re: [Capy review] Some questions
Steve Gerbino via Boost <[email protected]> Thu, 25 Jun 2026 16:23:06 +0000
| Newsgroups | gmane.comp.lib.boost.devel |
|---|---|
| Message-ID | <RYpfx2RyevrtuydddgVXCmlhWrxVMIGpUdYE_PnvH0gSYhAnkNT8KYUnXdoGioxBtzkdK6txlndtX68oKHrN8Ms8JJMGf3WhH92avJEErIM=@gerbino.co> |
On Thursday, June 25th, 2026 at 6:06 PM, Ruben Perez via Boost <[email protected]> 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. _______________________________________________ Boost mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/[email protected]/message/KG6THNZ4TZJOFNBAKEA3ZRUA2B4F27QS/