c# async await implementation [closed]

Question

I have some doubts about the design of C#'s upcoming async/await feature.

1. The convenience of attaching the new mechanism to Task<T>
2. I think is better to use async substituting the await keyword. For expaple: var result = async GetResultAsync();
3. The mechanism to cancel a ongoing async operation using a token is not as elegant as I feel it could be.

Async/away is a great feature, but I think it's not as well designed as LINQ. Also, I feel the desing team is dangerously pleased with the current design; and might not take community feedback into account.

What do you think?

Answer 1

These kind of design decisions tend to make little sense until you've tried to make this work yourself. Your assignment: write asynchronous code and make it stop whenever you want to. Your constraints: you cannot use Thread.Abort() and can never cause deadlock.

Answer 2

Async/away is a great feature, but I think it's not as well designed as LINQ.

What aspects of the design process do you feel are deficient compared to the design process for LINQ?

Also, I feel the design team is dangerously pleased with the current design; and might not take community feedback into account.

What gives you that impression? We've been inviting community feedback for quite some time now. It is not being ignored.

What do you think?

I think this is a discussion question and not an engineering question. Are you sure this is the right site for this question?