3 ms·
Hmm, the most popular C# IDEs (Visual Studio and Rider) don't have this problem - you can single step when debugging async code. Is there something in particul
by GordonS 6y ago
Hmm, the most popular C# IDEs (Visual Studio and Rider) don't have this problem - you can single step when debugging async code.
Is there something in particular about the JVM that makes it more difficult, or is it just that the work hasn't been done yet for some reason?
- yrio 6y agoI don't know about single step when debugging, but it seems intelligible stack trace for async code is available only recently, starting with .NET Core 2.1 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-...
- GordonS 6y agoIt was a long while back, so I can't be sure, but I seem to recall single step debugging and good stack traces being available since the first days of async/await, although there are some ways you can get yourself into situations where stack traces are near to worthless.