-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
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. |
Maybe these doc-comments should be on respective |
Reassigning to docs team — r? @GuillaumeGomez |
Sounds good. Thanks! @bors: r+ rollup |
📌 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.
Is there any chance this can be changed in a Rust edition? Eg the upcoming 2021 edition. |
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.