This brings to mind two thoughts.
1) Bikeshedding. It uses transform, and_then, or_else. I wonder to what degree we will end up discussing alignment on terminology.
2) I wonder if it is cleaner for us to follow p2300 with a paper to define connect and start for std::optional and get the sender algorithms on optional for free. It would give us co_await on an optional for free too, once co_await sender is defined for the task type, though not coroutine optionals in general.
This brings to mind two thoughts. 1) Bikeshedding. It uses
transform
,and_then
,or_else
. I wonder to what degree we will end up discussing alignment on terminology. 2) I wonder if it is cleaner for us to follow p2300 with a paper to defineconnect
andstart
forstd::optional
and get the sender algorithms on optional for free. It would give usco_await
on an optional for free too, onceco_await sender
is defined for the task type, though not coroutine optionals in general.