-
Notifications
You must be signed in to change notification settings - Fork 37
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
Forbid constant <op> constant comparisons for strings #229
Forbid constant <op> constant comparisons for strings #229
Conversation
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.
A couple of minor formatting suggestions, will approve now, please re-request review if you decide to commit them
Co-authored-by: Matthew Evans <[email protected]>
Thanks @ml-evs for the review and suggested improvements! They should be implemented now. |
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.
👍
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.
Looks good. I found a stray also
, and then I have a suggestion, which you can take or leave.
Co-Authored-By: Casper Welzel Andersen <[email protected]>
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.
Although I'd prefer grammar-based solution (no rule accepting string <operator> string
), I understand we expect to implement string vs. string comparisons in future releases, and this is told explicitly in the specification. Therefore I approve.
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 for implementing the suggested changes @rartino. And thanks for this clarification! 👍
Fixes #157.