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
Fix Parser::SyntaxError error with endless method for object equality #795
Labels
Comments
koic
added a commit
to koic/parser
that referenced
this issue
Apr 20, 2021
Fixes: whitequark#795. This PR fixes false positives that the comparison methods recognizes as a setter method.
koic
added a commit
to koic/parser
that referenced
this issue
Apr 20, 2021
Fixes: whitequark#795. This PR fixes false positives that the comparison methods recognizes as a setter method.
koic
added a commit
to koic/parser
that referenced
this issue
Apr 20, 2021
Fixes: whitequark#795. This PR fixes false positives that the comparison methods recognizes as a setter method.
koic
added a commit
to koic/parser
that referenced
this issue
Apr 20, 2021
Fixes: whitequark#795. This PR fixes false positives that non setter method ending with `=` recognizes as a setter method.
koic
added a commit
to koic/parser
that referenced
this issue
Apr 20, 2021
Fixes: whitequark#795. This PR fixes false positives that comparison methods recognizes as a setter method.
Thanks! 🙇 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
Discovered when attempting to write an endless method for object equality that I'd get a syntax error. Here's a snippet for illustration:
In this case, I'm using Reek to illustrate the stack dump in case it's helpful:
Reek Stack Dump
Steps to Recreate
You can recreate this issue quickly by saving this Ruby snippet to
snippet.rb
:...and then you can run the following to recreate the error:
Desired Behavior
I would like to be able to use an endless method since it's not assignment but equality that the parser is getting confused by.
Environment
The text was updated successfully, but these errors were encountered: