Apparently nobody noticed that Rust's output on panic has the location/message switched for 7.5 years
-
Show this thread
-
If you're not sure what I mean, it says > Thread 'name' panicked at 'msg', location when it should say > Thread 'name' panicked at location, 'msg'
2 replies 1 retweet 22 likesShow this thread -
Replying to @sgrif
well i'm gonna break a lot of panic output soon, maybe time to fix that :P
1 reply 0 retweets 2 likes -
Replying to @__anp__
I opened https://github.com/rust-lang/rust/pull/67034 … after being unable to find an issue and multiple folks saying they don't see any problem with fixing it (I expected to find a closed issue that was like "oh yeah this is wrong but there's tooling out there parsing this so we can't change it")
1 reply 0 retweets 6 likes -
Replying to @sgrif
nice! did you see ralf's post? https://www.ralfj.de/blog/2019/11/25/how-to-panic-in-rust.html … i suspect that the core panic impl might be trickier to make "nice"
1 reply 0 retweets 2 likes -
Replying to @__anp__
Yes, the reason I was looking at the file in the first place was because of that post. Core panic is fixed in the linked PR as well
1 reply 0 retweets 1 like -
Replying to @sgrif
Or I guess by "nice" you mean more than just swapping the arguments like I did.
1 reply 0 retweets 1 like -
`core::panic!` doesn't include a backtrace at all, so if any substantial changes are made to how the backtrace is displayed it wouldn't affect core. It'll probably just end up being the first line of whatever std outputs
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.