P3175 R0 Reconsidering the std::execution::on algorithm

[wg21bot]

P3175R0 Reconsidering the std::execution::on algorithm (Eric Niebler)

[inbal2l]

2024-04-16 Library Evolution Telecon

P3175R0: Reconsidering the std::execution::on algorithm

2024-04-16 Library Evolution Telecon Minutes

Champion: Eric Niebler
Chair: Fabio Fracassi
Minute Taker: Ben Craig

Summary

POLL: Rename std::execution::on to std::execution::start_on (P3175R0 Change 1)

SF	F	N	A	SA
5	7	1	1	0

Attendance: 18
Author's Position: SF
Outcome: Consensus in Favor

POLL: Rename std::execution::transfer to std::execution::continue_on (P3175R0 Change 2)

SF	F	N	A	SA
4	7	0	3	0

Attendance: 18
Author's Position: SF
Outcome: Consensus in favor

POLL: Add a new "on" algorithm with "scoped start_on semantic" (front) (P3175R0 Change 3)

SF	F	N	A	SA
3	9	2	0	0

Attendance: 18
Author's Position: SF
Outcome: Strong consensus in favor

POLL: Add a new "on" algorithm with "scoped continue_on semantic" (middle) (P3175R0 Change 7)

SF	F	N	A	SA
4	7	3	0	0

Attendance: 19
Author's Position: SF
Outcome: Strong consensus in favor

POLL: Rename read to read_env (part of P3175R0 Change 4)

SF	F	N	A	SA
12	2	0	0	0

Attendance: 19
Author's Position: SF
Outcome: Strong consensus in favor

POLL: POLL: Add a new adaptor write_env (part of P3175R0 Change 4)

SF	F	N	A	SA
2	7	3	0	1

Attendance: 19
Author's Position: SF
Outcome: Consensus in favor

POLL: POLL: Add a new adaptor unstoppable (P3175R0 Change 5)

SF	F	N	A	SA
1	6	5	0	1

Attendance: 19
Author's Position: WF
Outcome: Weak consensus in favor

POLL: Add a new algorithm finally and specify the default schedule_from in terms of it (P3175R0 Change 6)

SF	F	N	A	SA
3	5	4	0	1

Attendance: 19
Author's Position: SF
Outcome: Weak consensus in favor

SA: unconvinced that the majority of the people in the room understood the motivation or what we were voting on.

Paper forwarding checklist:

1. Why should this utility go into the standard library? improve API of an existing facility
2. Examples? yes
3. Discussion of prior art? yes
4. Implementation experience? yes
5. Usage experience? yes
6. Deployment experience? no
7. Performance considerations? n/a
8. Changes Library Evolution previously requested? n/a
9. Support in "std::format" and "hash" (if required)? n/a
10. Feature test macro? n/a
11. Freestanding? n/a
12. Wording? yes

Next Steps

The paper was reviewed and we approved: ::on, ::start_on, ::transfer, ::continue_on, ::on (+ scoped start_on semantic), ::on (+ scoped continue_on semantic), rename read to read_env.

In addition, we approved: adding adaptors: write_env, unstoppable, add a new algorithm finally and specifying the default schedule_from in its terms.

It was brought up in the reflector that the second list of items did not have enough discussion, we will briefly review it during the next LEWG meeting, before reviewing the wording and taking a forwarding poll.