-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Add take as alias for remove in collection methods #79943
Conversation
Should this happen for (Actually, I'm surprised to not see any |
☔ The latest upstream changes (presumably #81678) made this pull request unmergeable. Please resolve the merge conflicts. |
This partially alleviates the issues described in RFC 3034 [0] by adding a doc alias to `take` and `take_xxx` for `remove` and `remove_xxx`. [0]: rust-lang/rfcs#3034 r? @sfackler
@scottmcm Yeah, it does look like I rebased and added the missing aliases, if you don't mind taking a look. |
r? @m-ou-se |
r? @Amanieu |
Thanks for your PR and sorry for the late reply. This has been sitting still without review because it's not quite clear what exactly we want to use See #81989 (comment). For the specific aliases added in this PR, I'm wondering how useful they will be. These aliases are not displayed anywhere in the documentation, and only used when using the search functionality. I'd expect someone who is looking for methods on e.g. HashMap to be looking through the HashMap page, instead of entering just Anyway, as mentioned in the linked comment, we'd like to first reach some agreement on what kind of aliases we want and don't want before continuing merging PRs like this:
So, I'm closing this PR for now. Once we have a policy in place and this PR fits within it, feel free to re-open it. |
This partially alleviates the issues described in RFC 3034 [0] by adding
a doc alias to
take
andtake_xxx
forremove
andremove_xxx
.[0]: rust-lang/rfcs#3034
r? @sfackler