[close #75] Support endless method definition #80
+46
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When there is an "endless" method definition, we don't want to count it as having a keyword, otherwise when we try to expand it will search for a matching
endan possibly introduce a problem in the search.To detect this case I use the same logic introduced in ruby/irb@826ae90
For reference here are lex of a regular method definition (first line only) and then an "endless" definition:
The detection uses a state machine. It knows when it sees an
ENDFNstate that a function is being defined, but it's not known if it's a "regular" function or not. If theENDFNis followed by aBEGwith a token of=and then aENDthen it's assumed to be a full "oneliner" AKA "endless" method definition.