Allow Parser pattern size to be parametrizable #152
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
mbenedettini
commented
Jun 25, 2024
| numberFraction: /^[\.eE]/, | ||
| numberExponent: /^[eE]/, | ||
| numberExpSign: /^[-+]/ | ||
| }; | ||
| const MAX_PATTERN_SIZE = 16; |
There was a problem hiding this comment.
this const name is now confusing (compared to DEFAULT_PATTERN_SIZE) but I couldn't find a better name
|
@mbenedettini do you have any benchmarks showing that the speed of parsing had improved? I am asking because |
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.
When parsing files with big strings allowing a big pattern size can help shave off precious milliseconds making parsing considerably faster since less loops of the parser are needed, leaving the big lift to the Javascript Regexp engine.