-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
New lint: suspicious_unary_op_formatting #4615
Conversation
9c4ae63
to
9b2011e
Compare
9b2011e
to
589c20a
Compare
589c20a
to
4b2aaf2
Compare
4b2aaf2
to
9ab1958
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Waiting on travis.
You have to rerun |
9ab1958
to
b355d48
Compare
I did, but nothing changed. In fact I had made the changes by hand before discovering that the tool does them automatically. I deleted them and made them again with the tool, but nothing changed. Also, the error claims the list in |
☔ The latest upstream changes (presumably #4602) made this pull request unmergeable. Please resolve the merge conflicts. |
Oh yeah you have to rebase before running the script successfully. |
2cc972d
to
63ffbc4
Compare
Lints when, on the RHS of a BinOp, there is a UnOp without a space before the operator but with a space after (e.g. foo >- 1). Signed-off-by: Nikos Filippakis <[email protected]>
63ffbc4
to
5143fe1
Compare
Tests are passing :) |
@bors r+ |
📌 Commit 5143fe1 has been approved by |
New lint: suspicious_unary_op_formatting fixes #4228 changelog: New lint: [`suspicious_unary_op_formatting`]
☀️ Test successful - checks-travis, status-appveyor |
fixes #4228
changelog: New lint: [
suspicious_unary_op_formatting
]