4 ms·
I’ve been using async/await in .NET since it was an extension versus built in feature. It’s so much better than the old way of doing asynchronous programming us
by logbiscuitswave 5y ago
I’ve been using async/await in .NET since it was an extension versus built in feature. It’s so much better than the old way of doing asynchronous programming using delegates and callbacks. But, it’s not perfect - it works great, until it doesn’t. The moment you start needing to think about things like synchronization contexts (with ConfigureAwait), unexplained deadlocks, or debug them (which is still a pretty lousy experience) then it’s hard not to wish it wasn’t just a _little_ better.
It also has many footguns — especially how easy it is to make a seemingly asynchronous action blocking, and ‘async void’ can be a big bag of evil if you’re not careful.
I also really wish that chaining things together with ContinueWith wasn’t so clunky.
- hackerfromthefu 5y agoThankfully a community contributor fixed the issue with call stacks going missing on awaited exceptions too! Hopefully over time it keeps becoming that little bit better.