Bare identifiers now can start with reserved keywords as their prefix #189
Conversation
This file contains 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
dahlia
added
cmp:frontend
kanghyojun
previously approved these changes
Oct 24, 2017
dahlia
force-pushed
the
fix-identifier-parser
branch
from
d3f9ce0
to
93ed1ec
Compare
kanghyojun
approved these changes
Oct 26, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #184.
There had been a parser bug that bare identifiers (i.e. unquoted identifiers) cannot start with reserved keywords, e.g.
types(typeis reserved),enumeration(enumis reserved`). This patch fixes the bug.