You seem to know your way around coroutines, so I have a few questions for you.

First, std::execution::task doesn't seem to have a WhenAll primitive. How do I track the completion of specific coroutines within a task?

Also, where does the receiver fit into this picture? And what does a sender semantically represent in a coroutine context? For instance, if I'm dealing with Linux signals, would that be modeled as a sender or a receiver?

Finally, is std::execution actually ready for out-of-the-box usage?


At 2026-04-18 23:45:46, "Ville Voutilainen" <ville.voutilainen@gmail.com> wrote:
>On Sat, 18 Apr 2026 at 18:15, Zhao YunShan via Std-Proposals
><std-proposals@lists.isocpp.org> wrote:
>
>> I proposed this two years ago, and today, progress remains at zero.
>
>I'm sure you can provide a link to a P-numbered paper for that proposal then.
>
>> Since some claim that Interceptors are useful, why haven't they pushed to get this proposal into the Standard?
>> If the committee were truly serious about this, it wouldn't have taken this long, nor would they still be nitpicking.
>
>Since we are not in a position to teach you, you already know that the
>committee will not write a proposal for you.
>Therefore it's only logical that your question about why this hasn't
>been pushed into the standard must
>be rhetoric, and you already know the answer.