On 9/10/26 02:16, Jeff Garland via Boost wrote:
On Tue, Sep 8, 2026 at 8:05 AM Steve Gerbino <steve@gerbino.co> wrote:
As it exists today, Capy does not contain any OS-facing code. Capy does define execution_context which all executors derive from. All platform dependent code lives in Corosio -- which is why signals and the io_context live there.
Understood -- but this is a blocker for myself and at least one other reviewer. I *should* be able to write a service or a tool which is coroutine based and has cancelation without having to pull in all of Corosio. I see that as a pretty basic issue that means Capy doesn't have much future by itself. The way I see it, Corosio *is* io_context. If io_context is moved from Corosio to Capy, there won't be enough left in Corosio to justify a separate library.
-- Rainer Deyke - rainerd@eldwood.com