I have a simple function as the following:
static Task<A> Peirce<A, B>(Func<Func<A, Task<B>>, Task<A>> a)
{
var aa = new TaskCompletionSource<A>();
var tt = new Task<A>(() =>
a(b =>
{
aa.SetResult(b);
return new TaskCompletionSource<B>().Task;
}).Result
);
tt.Start();
return Task.WhenAny(aa.Task, tt).Result;
}
The idea is simple: for any implementation of a, it must return a Task<A> to me. For this purpose, it may or may not use the parameter (of type Func<A, Task<B>). If it do, our callback will be called and it sets the result of aa, and then aa.Task will complete. Otherwise, the result of a will not depend on its parameter, so we simply return its value. In any of the situation, either aa.Task or the result of a will complete, so it should never block unless a do not uses its parameter and blocks, or the task returned by a blocks.
The above code works, for example
static void Main(string[] args)
{
Func<Func<int, Task<int>>, Task<int>> t = a =>
{
return Task.FromResult(a(20).Result + 10);
};
Console.WriteLine(Peirce(t).Result); // output 20
t = a => Task.FromResult(10);
Console.WriteLine(Peirce(t).Result); // output 10
}
The problem here is, the two tasks aa.Task and tt must be cleaned up once the result of WhenAny has been determined, otherwise I am afraid there will be a leak of hanging tasks. I do not know how to do this, can any one suggest something? Or this is actually not a problem and C# will do it for me?
P.S. The name Peirce came from the famous “Peirce’s Law”(((A->B)->A)->A) in propositional logic.
UPDATE: the point of matter is not “dispose” the tasks but rather stop them from running. I have tested, when I put the “main” logic in a 1000 loop it runs slowly (about 1 loop/second), and creates a lot of threads so it is a problem to solve.
Thanks to @Bryan Crosby’s answer, I can now implement the function as the following:
and it works pretty well:
Now it is fast and not consuming to much resources. It can be even faster (about 70 times in my machine) if you do not use the async/await keyword:
Here the matter is, even you can detected the return value of
a(20), there is no way to cancel theasyncblock rather than throwing anOperationCanceledExceptionand it preventsWhenAnyto be optimized.UPDATE: optimised code and compared async/await and native Task API.
UPDATE: If I can write the following code it will be ideal:
Here,
await? a : bhas valuea‘s result if a successes, has value b if a is cancelled (likea ? b : c, the value ofa‘s result should have the same type of b).await breakwill cancel the current async block.