asyncawaaait

3 ms·

1. 1.▲
   by asyncawaaait 6y ago

   Stack traces were massively improved in 2.1. Using a good IDE (Rider or Visual Studio), debugging async/await code works as expected. Are you doing interop or calling unmanaged code?
2. 2.▲
   by asyncawaaait 6y ago

   There is a resource tradeoff. async/await has a minor CPU/memory impact, but it can also free up threads to do other work during an I/O bound operation. Threads have their own resource cost.
3. 3.▲
   by asyncawaaait 6y ago

   How does async/await introduce complexity where threading wouldn’t? In my experience, the complexity is vastly reduced by not having to implement tricky asynchronous APIs (Task Paralell, thread pools, BackgroundWorker, etc).
4. 4.▲
   by asyncawaaait 6y ago

   Awaiting a storage operation (ie. look up user) in C# will allow other calls to proceed until the I/O is available to read. Synchronous code locks you into the model of handling one request per thread. Given the minor overhead (both co