2024-06-24 SG1 St. Louis Meeting

P3296R1 let_async_scope

2024-06-24 SG1 in St Louis Minutes

Summary

Poll 1:
Should be specified to stop nested work on exception escaping the lambda passed to async scope or if the sender returned by that lambda did not succeed
4/6

Poll 2:
Environment provided to the let async scope should be inherited by the nested spawns
3/6
Poll 3:
Should explore a form of let async scope without a predecessor for use with co-routines
4/6

Next Steps

Require more discussion in SG1 (@ogiroux - please confirm).

P3296R1 let_with_async_scope (Anthony Williams)

P3296R2 let_async_scope (Anthony Williams)

P3296R3 let_async_scope (Anthony Williams)

2025-02-11 Library Evolution Hagenberg Meeting

P3296R3: let_async_scope

2025-02-11 Library Evolution Hagenberg Minutes

Champion: Anthony Williams / Ian
Chair: Inbal Levi / Robert Leahy
Minute Taker: Andreas

Summary

ACTION: Make “state-type” expo only type, remove the mutex (or replace it with atomic or explicitly specify the order) and get SG1’s wording except feedback on the phrasing.

ACTION: Modify the paper so that the environment provided to scope sender is propagated (special token is type scope_token)

ACTION: apply fixes and phrase the asynch scope concept.

POLL: Phrase asynchronous-scope concept (to be approved by LEWG, in reflector/telecon), apply the changes above and forward P3296R4 to LWG for C++26.

Attendance: 13 (IP) + 7 (R)
Author's Position: SF
Outcome: Weak consensus in favor (due to low participance)

Next Steps

Phrase asynchronous-scope concept (to be approved by LEWG, in reflector/telecon), apply the changes above and forward P3296R4 to LWG for C++26.

P3296R4 let_async_scope (Anthony Williams)