Re:What's new in the .NET 11 runtime
by tikotus on Tuesday November 10, 2026 @04:15PM
(#50446399)
Friendlier stack traces have an important upside: Cancellation is done by throwing exceptions, but you can't stop it from storing the full stack trace in a string. This can result in a noticeable hitch if the stack is very deep and complex. With a friendlier stack trace, I hope this issue is finally gone.
[ Parent
| on HN ]
As the article mentions, stack traces in exceptions are the one place where this change doesn't really move the needle: they were already hiding stack frames related to the async machinery in exception stack traces. The main benefit here is the live call stack in the debugger.
> One especially useful result is a clearer live call stack. Profilers and debuggers can show the asynchronous methods themselves instead of the infrastructure used to execute them. This is a distinction from exception stack traces, which already hide much of that infrastructure.