You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rust developers are developers. Many will be used to using a debugger. Lets tell them straight up from the panic! message how they can hook up their debugger without having to know anything about rust's name mangling algorithm.
The text was updated successfully, but these errors were encountered:
Used as workaround in #30625, but still discovered from other people instead of documentation. #30625. Mentioning rust_panic in the panic message and possibly in the documentation for panic! might be a good idea. If nobody is already doing this, I will :)
This splits the output of panics into two lines as proposed in #15239 and adds a
note about how to get a backtrace. Because the default panic message consists of
multiple lines now, this changes the test runner's failure output to not indent
the first line anymore.
Fixes#15239 and fixes#11704.
Rust developers are developers. Many will be used to using a debugger. Lets tell them straight up from the
panic!
message how they can hook up their debugger without having to know anything about rust's name mangling algorithm.The text was updated successfully, but these errors were encountered: