Variant keys can now be numbers, identifiers or quoted text #118
Conversation
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
stasm
force-pushed
the
remove-variant-names
branch
from
f4a11ad to
26ec384
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently, variant keys can either be numbers (
NumberExpressions) or text (VariantNames). Text keys allow inline whitespace; the whitespace at the extremes, however, is trimmed. Special characters like{or[are forbidden, but no escape sequences are allowed either.This PR changes variant keys to now be numbers (as before), identifiers (
Identifier) or quoted text (StringExpressions). TheVariantNameAST node has been removed.Fixes #90.