4 ms·
The state of async await tooling is shocking IMO. For anyone curious how bad it was, here’s a StackOverflow post from 2013 asking about intelligible async stac
by tybit 7y ago
The state of async await tooling is shocking IMO.
For anyone curious how bad it was, here’s a StackOverflow post from 2013 asking about intelligible async stack traces in C# with a proper solution not delivered until 2018 https://stackoverflow.com/questions/15410661/is-it-possible-to-get-a-good-stack-trace-with-net-async-methods https://stackoverflow.com/questions/15410661/is-it-possible-...
When it was finally delivered it was done by an amazing individual(Ben Adams) picking up the slack for Microsoft.
Last time I used Node in anger, last year, their async stack traces were even worse, losing the stack traces at the await point. Hopefully they’ve fixed it by now.