Uh oh!
There was an error while loading. Please reload this page.
Document non-obvious behavior of fmt::UpperHex & co for negative integers - #46285
Conversation
…gers Before stabilization I’d have suggested changing the behavior, but that time is past.
rust-highfive
commented
Nov 26, 2017
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
SimonSapin
commented
Nov 26, 2017
Maybe these doc-comments should be on respective |
kennytm
commented
Nov 27, 2017
Reassigning to docs team — r? @GuillaumeGomez |
GuillaumeGomez
commented
Nov 27, 2017
Sounds good. Thanks! @bors: r+ rollup |
bors
commented
Nov 27, 2017
📌 Commit a326d8d has been approved by |
…aumeGomez Document non-obvious behavior of fmt::UpperHex & co for negative integers Before stabilization I’d have suggested changing the behavior, but that time is past.
cmcqueen
commented
Jun 23, 2021
Is there any chance this can be changed in a Rust edition? Eg the upcoming 2021 edition. |
kennytm
commented
Jun 23, 2021
No, the runtime behavior is edition-agnostic in the since they share the same libcore. That means we either change it for all of 2015/2018/2021 starting from Rust 1.XX or never change it. |
Before stabilization I’d have suggested changing the behavior, but that time is past.