-
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
reword descriptions of the deprecated int modules #107654
Conversation
r? @thomcc (rustbot has picked a reviewer for you, use r? to override) |
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, "redundant" is a good choice I think, instead of "deprecated" which we cannot use unless we deprecate.
Yeah my main reason for not using "deprecated" is because it says it's deprecated right there already. |
Looks great @bors r+ rollup |
Rollup of 7 pull requests Successful merges: - rust-lang#107654 (reword descriptions of the deprecated int modules) - rust-lang#107915 (Add `array::map` benchmarks) - rust-lang#107961 (Avoid copy-pasting the `ilog` panic string in a bunch of places) - rust-lang#107962 (Add a doc note about why `Chain` is not `ExactSizeIterator`) - rust-lang#107966 (Update browser-ui-test version to 0.14.3) - rust-lang#107970 (Hermit: Remove floor symbol) - rust-lang#107973 (Fix unintentional UB in SIMD tests) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Based on recommendation by @est31 here: #107587 (comment)
This is meant to make it more clear, when looking at the
std
orcore
docs, that these are deprecated modules - not deprecated integer types (a common misunderstanding).Before:
After: