Is it possible to avoid `return await` in branches that delegate to a Task with the same return type?
I have an asynchronous method to handle aggregated requests. It basically breaks up the requests into single ones, handled by another method with the same return type, and combines the answers into a single response. In case the aggregate request actually consists only of a single request, I can delegate directly to the second method.
When to use Task in Interface Methods in C#?
There are interface methods that you obviously know that will be async
, implementations that will read from the disk for example, you can easily decide to use Task
. There are also interface methods that might use async
, you can make them return Task
too.
When to use Task in Interface Methods in C#?
There are interface methods that you obviously know that will be async
, implementations that will read from the disk for example, you can easily decide to use Task
. There are also interface methods that might use async
, you can make them return Task
too.
When to use Task in Interface Methods in C#?
There are interface methods that you obviously know that will be async
, implementations that will read from the disk for example, you can easily decide to use Task
. There are also interface methods that might use async
, you can make them return Task
too.
When to use Task in Interface Methods in C#?
There are interface methods that you obviously know that will be async
, implementations that will read from the disk for example, you can easily decide to use Task
. There are also interface methods that might use async
, you can make them return Task
too.
When to use Task in Interface Methods in C#?
There are interface methods that you obviously know that will be async
, implementations that will read from the disk for example, you can easily decide to use Task
. There are also interface methods that might use async
, you can make them return Task
too.
When to use Task in Interface Methods in C#?
There are interface methods that you obviously know that will be async
, implementations that will read from the disk for example, you can easily decide to use Task
. There are also interface methods that might use async
, you can make them return Task
too.
When to use Task in Interface Methods in C#?
There are interface methods that you obviously know that will be async
, implementations that will read from the disk for example, you can easily decide to use Task
. There are also interface methods that might use async
, you can make them return Task
too.
When to use Task in Interface Methods in C#?
There are interface methods that you obviously know that will be async
, implementations that will read from the disk for example, you can easily decide to use Task
. There are also interface methods that might use async
, you can make them return Task
too.
When to use Task in Interface Methods in C#?
There are interface methods that you obviously know that will be async
, implementations that will read from the disk for example, you can easily decide to use Task
. There are also interface methods that might use async
, you can make them return Task
too.