Skip to main content

Task.Unwrap() - A useful proxy to avoid inner Task inside a Task

In this post we will talk about Task and what we should do when we end up with 'Task<Task<Foo>>".

Let's start with a simple example. Let's asume that we have an async method.
public async Task<int> DoSomethingAsync()
{
    return await GetNumberAsync();
}
We have the 'DoSomethingAsync' method that we need to call inside another task. If we call this method directly we will end up with Task<int>, but if we call this method in another Task than we will end up with...
Task<int> simpleCall = DoSomethingAsync();

Task<Task<int>> complexCall = new Task<Task<int>>(
    async () =>
    {
        return await DoSomethingAsync();
    });
As we can see, to be able to call a async a method in a task we will need to add the 'async' attribute to the lambda expression (function). Because of this we will get a Task of Task (Task<Task<..>) and not a simple Task<...>.

You could say that this is fine, it is not complicated to get the result of the inner task and so on. Yes, this is true, but in the same time we need to be able to handle error from both tasks and cancelation tokens.
For this cases it is recommended to use "Task.Unwrap" method, that allow us to work directly with Task<...>.
Task<int> simpleCall = DoSomethingAsync();

Task<Task<int>> complexCall = new Task<Task<int>>(
    async () =>
    {
        return await DoSomethingAsync();
    });
complexCall.Start();
Task<int> complexCallUnwrap = complexCall.Unwrap();
There is no magic behind 'Unwrap' method. You can use with success in cases when you have Task<Task<Task<...>,  also.
Behind the scene, 'Unwrap' method creates a proxy that will handle all complex cases for us. We don't need to forward the cancelation token, to check errors at different level. We can work as we would have a simple task, not a task inside another tasks.
The Task that is returned by 'Unwrap' includes all the cancelation token request and exception handling (the proxy is doing the job of connecting the task with inner task).

Another use case when 'Unwrap' is useful is in the moment when we want to create a continue action using 'ContinueWith' method. Without 'Unwrap' method we can end up easily in cases where we have inner Task inside a task. This can be avoided using 'Unwrap'.
Task<Task<int>> taskInTask = DoSomethingAsync()
                                .ContinueWith((value) => DoSomethingAsync());
Task<int> taskInTaskWithUnwrap = DoSomethingAsync()
                                            .ContinueWith((value) => DoSomethingAsync())
                                            .Unwrap();

Using 'Unwrap' method we can work directly with a proxy, that represents the entire Task<Task>, like a simple Task.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...