RegularParser block tokens #61
Merged
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
thunderer
force-pushed
the
regular-parser-block-tokens
branch
from
2fff329
to
fdc6ce8
Compare
…ingle string instead of each character separately
thunderer
force-pushed
the
regular-parser-block-tokens
branch
from
fdc6ce8
to
6234af9
Compare
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.
Tokenizer in RegularParser broke down the text into single characters or words (with some exceptions) regardless of the token type. This PR improves the tokenizer regex to report the text fragments without syntax tokens as single string tokens which should improve performance and reduce idle string joining operations in the parsing process, especially in real-world use cases with long texts with few shortcodes inside.