Re: Capy Review

Vinnie Falco via Boost <[email protected]> Mon, 29 Jun 2026 12:53:16 -0700

Newsgroups	gmane.comp.lib.boost.devel
Message-ID	<CA+EzHGdPOZ4eR0B8B2KkCoVYSng6N0HCOUyj4qN3zd+HWNm=oQ@mail.gmail.com>

On Mon, Jun 29, 2026 at 12:36 PM Ian Petersen via Boost <
[email protected]> wrote:

> We already have std::execution::get_stop_token and
> std::execution::get_scheduler (which are analogous to but different from
> the stop token and executor members in the proposed IoAwaitable); my own
> paper, P4223, directly inspired by Vinnie et al's work on Capy, proposes
> std::execution::get_frame_allocator. I suspect that the interop problem
> would be greatly ameliorated if Capy made use of the existing, standard
> context-sharing protocol, no?
>

First welcome to the Boost Formal Review of Capy and Corosio :) Thanks for
visiting.

Now, does P2300 define any awaitable types?

Regards
_______________________________________________
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/SMZLZ5YTOSV6JXCFO2ETDVK4X2ILT5AW/