I can imagine a few ways that yielding an error (or Promise rejection) should be handled
Treat it like any other value
Task is still "successful"
.error is not set
Treat is like a thrown error
Task enters the "error" state
.error is set to the thing that was Promise's rejection value
I'm not sure which makes more sense -- currently 1 is how it is handled, but I would like to get input ton other perspectives on how it should be handled.
I can imagine a few ways that yielding an error (or
Promise
rejection) should be handled.error
is not set.error
is set to the thing that was Promise's rejection valueI'm not sure which makes more sense -- currently
1
is how it is handled, but I would like to get input ton other perspectives on how it should be handled.