support for <expr> by <expr> loops - #837
Merged
Merged
Conversation
Contributor
|
Can you please add a test with said special case? I'll merge it after that :) |
Collaborator
Author
|
It already exists! |
Contributor
|
Ah ok, you merely added it for that. |
vendethiel
added a commit
that referenced
this pull request
Feb 2, 2016
support for <expr> by <expr> loops
Contributor
|
Thanks again! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It was already in the grammar, but the lexer was written such that it could never happen.
As a special case,
for by in foostill treatsbyas an identifier rather than a keyword.