-
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
Fixes #39661 #39662
Fixes #39661 #39662
Conversation
Clarified potential ambiguity.
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @BurntSushi (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. |
Looks great! Thank you so much! @bors: r+ rollup |
📌 Commit 51ef003 has been approved by |
Hm, I think there should be an article before "map". |
@euclio Ah, missed that. How about "a"? |
Fixes rust-lang#39661 Clarifies the potential ambiguity.
Looks good, thanks for your contribution! @bors r+ rollup |
📌 Commit 8251a2d has been approved by |
Fixes rust-lang#39661 Clarifies the potential ambiguity.
Clarifies the potential ambiguity.