expr: Fix parsing range quantifiers in regex #7997
Merged
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
frendsick
force-pushed
the
fix/expr-regex-range-quantifiers
branch
from
09ed38d to
aae6207
Compare
frendsick
force-pushed
the
fix/expr-regex-range-quantifiers
branch
from
68b5da5 to
837bab2
Compare
Contributor
|
Thanks! |
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.
Fix parsing the following special cases for range quantifiers in the regex of the
exprcommand.\{,\}zero or more\{,6\}six or lessThis PR also enables the rest of the ignored
test_bre*tests and removes redundant escaping of the '*' character.fixes #7664