2025-02-13 Library Evolution Hagenberg Meeting

P3552R0: Add a Coroutine Lazy Type

2025-02-13 Library Evolution Hagenberg Minutes

Champion: Dietmar Kühl / Maikel Nadolski
Chair: Inbal Levi / Fabio Fracassi
Minute Taker: Eddie Nolan

Summary

POLL: Use the name “std::execution::task” (instead of lazy)

SF	F	N	A	SA
10	13	1	0	0

Attendance: 33 (IP) + 7 (R)
Author's Position: SF
Outcome: Consensus in favor

POLL: Change continue_on into affinity_on (yielding logic for either finishing inline (if possible) or rescheduling to the utility according to scheduler properties)

SF	F	N	A	SA
9	6	2	1	0

Attendance: 33 (IP) + 7 (R)
Author's Position: F
Outcome: Consensus in favor

A: My concern is people might dig their own holes by doing it and being explicit is easier.

POLL: Support for errors without exceptions (pushing it to set_error)

SF	F	N	A	SA
6	6	4	1	1

Attendance: 33 (IP) + 7 (R)
Author's Position: 2xSF
Outcome: Consensus in favor

SA: I think we can make it work in an efficient manner with examining exception_ptr paper that’s in flight, and the promise of optimizing short circuit exceptions.
A: One reason to do that is to run coroutines that don’t have exceptions.

Next Steps

Author got feedback on R0, paper will be seen again by LEWG.

P3552 R3 Add a Coroutine Task Type #2200

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions