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
Does your perception change if you think of it as 'step' or 'marker' (rather than 'msg') followed by more technical location detail?
1 reply 0 retweets 0 likes -
Replying to @redtwitdown
Nope, it still sounds wrong (and I went code spelunking to find where it was introduced to see that it was not intentional, which is why I know it's been 7.5 years)
1 reply 0 retweets 0 likes -
Replying to @sgrif
Fair enough. That's (roughly) how I've always thought of it.. go look for 'msg' as a named part of the location. Until you altered my perception in the other direction .. :)
1 reply 0 retweets 1 like -
Replying to @redtwitdown
Yeah, I think most folks (myself included) just assumed it was an awkwardly phrased sentence. Was looking at the line today though and thought "this is way to easy for the message to have been changed but the arg order forgot to be changed for that not to be what happened".
1 reply 0 retweets 1 like -
Replying to @sgrif @redtwitdown
great example of why we should (but won't) name fmt args
1 reply 0 retweets 0 likes -
Replying to @myrrlyn @redtwitdown
The bug was actually originally introduced in C++ code!
1 reply 0 retweets 2 likes -
Replying to @sgrif @redtwitdown
fair enough, C++ printing excuses all errors
1 reply 0 retweets 0 likes
My point was more that the rust code is an artifact of moving this code over from C++ exactly as written, not an explicit decision to avoid named args
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.