-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Replace libstd, libcore, liballoc terminology in docs #103707
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @m-ou-se (or someone else) soon. Please see the contribution instructions for more information. |
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
@bors r=H4x5 |
@jonathanCogan: 🔑 Insufficient privileges: Not in reviewers |
☔ The latest upstream changes (presumably #104999) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors r+ |
📌 Commit e2166188100f3a84ab49003193b5034fcc469fbb has been approved by It is now in the queue for this repository. |
@bors r+ |
…iaskrgr Rollup of 4 pull requests Successful merges: - rust-lang#99244 (doc: clearer and more correct Iterator::scan) - rust-lang#103707 (Replace libstd, libcore, liballoc terminology in docs) - rust-lang#104182 (`IN6ADDR_ANY_INIT` and `IN6ADDR_LOOPBACK_INIT` documentation.) - rust-lang#106273 (rustdoc: remove redundant CSS `.source .content { overflow: visible }`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Fixes #103551. I changed line comments containing the outdated terms as well.
It would be great if someone with more experience could weigh in on whether these changes introduce ambiguity as suggested in #103551 (comment).