P2202 Executors Review Reports: Sender/Receiver Concepts

[wg21bot]

P2202R0 Senders/Receivers group Executors review report (Gašper Ažman, Tony van Eerd, Thomas Rodgers, Tomasz Kamiński, Corentin Jabot, Robert Leahy, Gordon Brown, Kirk Shoop, Eric Niebler, Dietmar Kühl)

[brycelelbach]

2020-06-29 and 2020-07-07 Library Evolution Review

2020-06-29 and 2020-07-07 Library Evolution Minutes - D2202R0 Executors Review Report: Sender/Receiver Concepts

Chair: Nevin Liber and Fabio Fracassi

Champion: Gašper Ažman

Minute Taker: Ben Craig

2020-07-07 Library Evolution Minutes - D2203R0 Executors Review Report: Customization Points

Chair: Fabio Fracassi

Champion: Ryan McDougall

Minute Taker: Ben Craig

Summary

We reviewed D2022R0 Sender/Receiver Review Report and D2203R0 Customization Point Report
The Sender/Reciever report will be compiled into concrete questions to be polled at a later date.

POLL: We want to make the selection of Executor <-> Scheduler interoperation adapters more explicit and not provide implicit defaults (esp. setting terminate as the error channel when calling the execute cpo). Given the history of the consensus of R0443 this would need a paper.

Strongly For	Weakly For	Neutral	Weakly Against	Strongly Against
2	16	5	2	1

SA: The poll was taken without the primary dissenter

Attendance: 27

# of Authors: 8

Outcome

This and the previous session were mostly informational, to identify open questions and make sure that we properly understand the programming model that we are integrating with Executors and Sender/Receivers.

One outcome is that we need lots of additional documentation and examples to make informed decisions, since the programming model (and the domain) is complex. Also to evaluate the proposed concepts we need to understand the algorithms in P1897 or P1898.

Most open issues we discovered seem to be at the seams and interactions between the two models Sender/Receiver and Executors, especially in the way that errors and cancelations are propagated between the two models.