Stephen_Cleary

Thanks for the great video, guys! It's nice to know the underlying data structures.

Just one question (for the interviewer): how is async being overused?

       -Steve

@KarlZ: You can unit test asynchronous code in VS2012 with MSTest or xUnit by declaring your unit tests as "async Task" instead of "void".

Thanks, guys! Great content!

In particular, thanks for not just showing "what works" but also the pitfalls.

Just a couple of notes:

1. WhenAll will actually return the results of those tasks. So you can replace:
       await Task.WhenAll(results);
       return results.Select(t => t.Result);
   with:
       return await Task.WhenAll(results);
2. I recommend that async/await users never use Task.Result (for the reasons you mentioned). There's a bit of overhead to use "await task" instead of "task.Result" on a completed Task, but the code is more obviously correct.

       -Steve

Awesome talk, Stephen! Wish I could have been there in person!

Thank you in particular for going "deep".

One quick question re your demo where Wait causes a deadlock: is that a change in behavior? I haven't tried it, but from my understanding of http://blogs.msdn.com/b/pfxteam/archive/2009/10/15/9907713.aspx, I would expect Wait to run the task inline in this scenario.