Await on a completed task same as task.Result?

by

There are already some good answers/comments here, but just to chime in…

There are two reasons why I prefer await over Result (or Wait). The first is that the error handling is different; await does not wrap the exception in an AggregateException. Ideally, asynchronous code should never have to deal with AggregateException at all, unless it specifically wants to.

The second reason is a little more subtle. As I describe on my blog (and in the book), Result/Wait can cause deadlocks, and can cause even more subtle deadlocks when used in an async method. So, when I’m reading through code and I see a Result or Wait, that’s an immediate warning flag. The Result/Wait is only correct if you’re absolutely sure that the task is already completed. Not only is this hard to see at a glance (in real-world code), but it’s also more brittle to code changes.

That’s not to say that Result/Wait should never be used. I follow these guidelines in my own code:

  1. Asynchronous code in an application can only use await.
  2. Asynchronous utility code (in a library) can occasionally use Result/Wait if the code really calls for it. Such usage should probably have comments.
  3. Parallel task code can use Result and Wait.

Note that (1) is by far the common case, hence my tendency to use await everywhere and treat the other cases as exceptions to the general rule.

More Related Contents:

  1. When correctly use Task.Run and when just async-await
  2. How can I call an async method in Main?
  3. Asynchronous Task.WhenAll with timeout
  4. Why use async and return await, when you can return Task directly?
  5. Should I worry about “This async method lacks ‘await’ operators and will run synchronously” warning
  6. Await vs Task.Result in an Async Method [duplicate]
  7. How to limit the amount of concurrent async I/O operations?
  8. WaitAll vs WhenAll
  9. HttpClient.GetAsync(…) never returns when using await/async
  10. Running multiple async tasks and waiting for them all to complete
  11. Async/await with/without awaiting (fire and forget)
  12. Why does this async action hang when I try and access the Result property of my Task?
  13. Difference between await and ContinueWith
  14. How to wait for async method to complete?
  15. Waiting for async/await inside a task
  16. Async and await – difference between console, Windows Forms and ASP.NET
  17. Benefits of using async and await keywords
  18. Await in catch block
  19. async await return Task
  20. Executing tasks in parallel
  21. Proper way to start and fire-and-forget asynchronous calls?
  22. Use Task.Run() in synchronous method to avoid deadlock waiting on async method?
  23. A pattern for self-cancelling and restarting task
  24. A pattern to pause/resume an async task?
  25. Converting async/await to Task.ContinueWith
  26. How to Async Files.ReadAllLines and await for results?
  27. I thought await continued on the same thread as the caller, but it seems not to
  28. How do I create a custom SynchronizationContext so that all continuations can be processed by my own single-threaded event loop?
  29. Is it possible to get successful results from a Task.WhenAll when one of the tasks fails? [duplicate]
  30. call async method without await #2

Leave a Comment