-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Convert 'may not' to either 'must not' or 'might not' in the standard library documentation #83584
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
Comments
@rustbot claim |
@rustbot claim |
Oh......I completely forgot about that hahahah |
I'm trying to create a new branch but i'm getting a |
@amalik18 are you trying to download using SSH? Use HTTP instead: |
Yep using HTTPS. I even generated a public access token. Still getting the error:
|
@amalik18 can you join the Zulip so I can help you debug this without spamming the issue tracker? https://rust-lang.zulipchat.com/ |
Thanks for working on this! |
"may not" has two possible meanings:
In some cases, the meaning is ambiguous: "Some cars may not have snow
tires." (do the cars happen to not have snow tires, or is it
physically impossible for them to have snow tires?)
It would be better to change places where the standard library uses the "description of
fact" meaning to say "might not" instead, and change the "command" meaning to "must not".
You can find places where "may not" is used like so:
Originally posted by @jyn514 in #83582
The text was updated successfully, but these errors were encountered: