On Tue, Sep 8, 2026 at 8:05 AM Steve Gerbino <steve@gerbino.co> wrote:
*1c* Adding to Capy - io_context and signal handling?
From my professional experience writing servers purely with coroutines the io_context is the key to making signals, networking, file-io all go together smoothly. As such it seems like that fundamental construct should be in Capy.
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. Jeff