Resolve parser states at once instead of resolving them iteratively. #3875
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
fruffy
force-pushed
the
parser_states
branch
3 times, most recently
from
00d7029 to
ffec344
Compare
fruffy
force-pushed
the
parser_states
branch
5 times, most recently
from
7dec20c to
298d773
Compare
Merged
fruffy
requested review from
fruffy,
pkotikal,
vhavel,
jnfoster and
mihaibudiu
as code owners
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.
Instead of stepping into a parser state, then removing it from the select expression, we just iterate over all select matches and construct the respective conditions all at once.