-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
Remove some unnecessary parens in assert! conditions
#135945
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
Conversation
|
rustbot has assigned @compiler-errors. Use |
|
The Miri subtree was changed cc @rust-lang/miri |
|
☔ The latest upstream changes (presumably #135937) made this pull request unmergeable. Please resolve the merge conflicts. |
5cf9105 to
1363cd4
Compare
|
☔ The latest upstream changes (presumably #136533) made this pull request unmergeable. Please resolve the merge conflicts. |
|
@rustbot author r=me after rebasing |
While working on rust-lang#122661, some of these started triggering our "unnecessary parens" lints due to a change in the `assert!` desugaring. A cursory search identified a few more. Some of these have been carried from before 1.0, were a bulk rename from the previous name of `assert!` left them in that state. I went and removed as many of these unnecessary parens as possible in order to have fewer annoyances in the future if we make the lint smarter.
1363cd4 to
3815ed6
Compare
|
@bors r=compiler-errors |
While working on #122661, some of these started triggering our "unnecessary parens" lints due to a change in the
assert!desugaring. A cursory search identified a few more. Some of these have been carried from before 1.0, were a bulk rename from the previous name ofassert!left them in that state. I went and removed as many of these unnecessary parens as possible in order to have fewer annoyances in the future if we make the lint smarter.