Re: Capy Review

Rainer Deyke wrote:
> On 6/27/26 02:05, Vinnie Falco via Boost wrote:
> 
> > The real solution is: everyone agrees on a protocol for propagating
> > executor + stop token + allocator. Then one bridge covers everyone.
> > That is IoAwaitable. Or, more poignantly:
> >
> >      std::io_awaitable
> 
> And that's the solution I'm looking for.  But I'm told this is outside the scope of
> Capy, which should only be used for socket-based i/o using corosio.

This has to be a misunderstanding. Establishing this protocol and testing
it in practice was definitely a goal for Capy, and the most important one (for
me at least.)


_______________________________________________
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/Q2E3MZHDWSUCDHKOGA3GOMJINOUSFLRI/