What’s the difference between returning void and returning a Task?

by

SLaks and Killercam’s answers are good; I thought I’d just add a bit more context.

Your first question is essentially about what methods can be marked async.

A method marked as async can return void, Task or Task<T>. What are the differences between them?

A Task<T> returning async method can be awaited, and when the task completes it will proffer up a T.

A Task returning async method can be awaited, and when the task completes, the continuation of the task is scheduled to run.

A void returning async method cannot be awaited; it is a “fire and forget” method. It does work asynchronously, and you have no way of telling when it is done. This is more than a little bit weird; as SLaks says, normally you would only do that when making an asynchronous event handler. The event fires, the handler executes; no one is going to “await” the task returned by the event handler because event handlers do not return tasks, and even if they did, what code would use the Task for something? It’s usually not user code that transfers control to the handler in the first place.

Your second question, in a comment, is essentially about what can be awaited:

What kinds of methods can be awaited? Can a void-returning method be awaited?

No, a void-returning method cannot be awaited. The compiler translates await M() into a call to M().GetAwaiter(), where GetAwaiter might be an instance method or an extension method. The value awaited has to be one for which you can get an awaiter; clearly a void-returning method does not produce a value from which you can get an awaiter.

Task-returning methods can produce awaitable values. We anticipate that third parties will want to create their own implementations of Task-like objects that can be awaited, and you will be able to await them. However, you will not be allowed to declare async methods that return anything but void, Task or Task<T>.

(UPDATE: My last sentence there may be falsified by a future version of C#; there is a proposal to allow return types other than task types for async methods.)

(UPDATE: The feature mentioned above made it in to C# 7.)

More Related Contents:

  1. How to limit the amount of concurrent async I/O operations?
  2. WaitAll vs WhenAll
  3. Catch an exception thrown by an async void method
  4. Running multiple async tasks and waiting for them all to complete
  5. Run two async tasks in parallel and collect results in .NET 4.5
  6. Calling async method synchronously
  7. Why does this async action hang when I try and access the Result property of my Task?
  8. Best way in .NET to manage queue of tasks on a separate (single) thread
  9. Task sequencing and re-entracy
  10. Enforce an async method to be called once
  11. Best way to convert callback-based async method to awaitable task
  12. Why does the async keyword exist
  13. Executing tasks in parallel
  14. Why was “SwitchTo” removed from Async CTP / Release?
  15. Calling async methods from non-async code
  16. Use Task.Run() in synchronous method to avoid deadlock waiting on async method?
  17. A pattern for self-cancelling and restarting task
  18. What is the correct way to cancel an async operation that doesn’t accept a CancellationToken?
  19. ForEachAsync with Result
  20. How can I capture the value of an outer variable inside a lambda expression?
  21. Converting async/await to Task.ContinueWith
  22. How to throttle multiple asynchronous tasks?
  23. Synchronous implementation of interface that returns Task
  24. Is it possible to get successful results from a Task.WhenAll when one of the tasks fails? [duplicate]
  25. can not await async lambda
  26. Why use async requests instead of using a larger threadpool?
  27. HttpClient.SendAsync using the thread-pool instead of async IO?
  28. How to implement Task.WhenAny() with a predicate
  29. Calling TaskCompletionSource.SetResult in a non blocking manner
  30. ConfigureAwait pushes the continuation to a pool thread

Leave a Comment