-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how error handling works #76
Comments
I would also be interested in this. |
The code behaves as if the call to While
However, that won't work because (From what I've read of the code, most of the work will be to construct the right kind of Tryy. Why is there even a Tryy type if both implementations use scala.util.Try?) |
+1 to tryAwait at least until proper try/catch handling is supported |
This would be much appreciated! |
I was playing with async/await and this is one of the first questions that popped up. So 👍 to improve this. |
FWIW I used @danarmak's solution above: await(kittens() map Success.apply recover PartialFunction(Failure.apply)) match {
case Failure(t) ⇒ // ...
case Success(v) ⇒ // ...
} But a |
How are failed futures handled? Does the whole
async
block just fail? Is there a way to handle individual failedawait
s within oneasync
block, or is the only solution there to nestasync
blocks? If that's the case, perhaps atryAwait
that returns aTry
would be helpful. In any case, a couple examples in the docs would be great. ThanksThe text was updated successfully, but these errors were encountered: