3 ms·
C++26 adopted senders/receivers (std::execution) as its official concurrency model, with the explicit aim of supporting structured concurrency. See https://www.
by spacechild1 2mo ago
C++26 adopted senders/receivers (std::execution) as its official concurrency model, with the explicit aim of supporting structured concurrency. See https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p2300r10.html https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p23...
- simonask 2mo agoSkimming the proposal, that looks like the equivalent of the "executor" (scheduler) and "task" (sender) implemented in Rust async runtimes. I could have missed it, but I don't see anything in particular to help with managing structured concurrency? Like, the central challenge is cancellation: In structured concurrency, subtasks spawned from a parent task must finish cancelling before the parent task can be cancelled.
- spacechild1 2mo agohttps://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p2300r10.html#design-cancellation https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p23...