Skip to content
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

clarify message for non-obvious precedence #14043

Merged
merged 1 commit into from
Jan 23, 2025
Merged

Conversation

jhpratt
Copy link
Member

@jhpratt jhpratt commented Jan 20, 2025

I ran across this message while writing code and thought it was quite odd. I've simplified it and hopefully made it clearer for non-native English speakers.

changelog: clarify message for non-obvious precedence

@rustbot
Copy link
Collaborator

rustbot commented Jan 20, 2025

r? @Centri3

rustbot has assigned @Centri3.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties label Jan 20, 2025
@@ -43,7 +43,7 @@ impl EarlyLintPass for Precedence {
cx,
PRECEDENCE,
expr.span,
"operator precedence can trip the unwary",
"operator precedence may not be obvious",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're gonna be really pedantic, this could also be read as if it is not allowed to be obvious. I prefer this, but If we're here already, I'd say to use might not instead

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch; you're absolutely right. I've changed it to "might not".

@Centri3 Centri3 added this pull request to the merge queue Jan 23, 2025
Merged via the queue into rust-lang:master with commit 92fac5c Jan 23, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants