Re: [Capy review] Some questions

> > 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.

This needs to go in a red banner at the top of Corosio's documentation.

Also, asking whether a feature X that has been brought before is
implementable with the current library architecture is completely in
scope of a Boost review.

Thanks,
Ruben.
_______________________________________________
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/N7DKPA24437BBOTAIAPABKN2DLXWCZTZ/