KQL: swap around order of comparisons to reduce local ambiguity#526
Open
lolbinarycat wants to merge 1 commit intokdl-org:mainfrom
Open
KQL: swap around order of comparisons to reduce local ambiguity#526lolbinarycat wants to merge 1 commit intokdl-org:mainfrom
lolbinarycat wants to merge 1 commit intokdl-org:mainfrom
Conversation
generally in {A,E}BNF, if one literal is a prefix of another,
the longer one is specified first, otherwise the shorter one
will always match, either causing a spurious error or a parsing
ambiguity, unless using a parser architecture which automatically
resolved local ambiguities by collecting alternatives.
this is something the rest of the KDL and KQL specs do well,
but it seems this case slipped through the cracks.
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
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.
generally in {A,E}BNF, if one literal is a prefix of another, the longer one is specified first, otherwise the shorter one will always match, either causing a spurious error or a parsing ambiguity, unless using a parser architecture which automatically resolved local ambiguities by collecting alternatives.
this is something the rest of the KDL and KQL specs do well, but it seems this case slipped through the cracks.