<@U2E974ELT> How will that help with awaiting for ...
# coroutines
d
@elizarov How will that help with awaiting for the first actually successful coroutine? Never failing one will still have to return something — some "empty" value I guess. Or do you mean keeping this approach but simplifying it by calling self in
onAwait
instead of
catch
in the case
result
is "empty"? I'm actually interested in the failures in some cases, so I need to somehow pass them through anyway to inspect them later.
e
Good point!