exec::finally()
shouldn't include std::exception_ptr
in the error types if neither the source or final senders include that error type
#1335
Labels
discussion
We need to talk about this; there's nothing actionable here yet
I would have expected the following code to compile, but it fails because
let_error
tries to instantiate a call to the lambda with an argument of typestd::exception_ptr
.https://godbolt.org/z/PK8YjohW8
I suspect that this is because we don't know ahead of time whether
connect()
is potentially throwing.We could potentially work around this by instead connecting the final-sender at connect-time of the
finally
sender. This way, we know that we will be able start the final-operation when the input operation completes regardless of whether theconnect()
method is throwing or not.The text was updated successfully, but these errors were encountered: