Fixes for issues with multichar newline #2233
Open
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
Add support for filling the buffer in a way that can be peeked ahead to confirm what state the parser should be in.
fwilliamconceicao
approved these changes
Feb 19, 2024
|
I rewrote the parser from scratch and will be releasing it soon. It works completely different. I'll leave this hear until then though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Contains fixes for the issues described in #2216, have verified this solves all our problems in our own testing.
Added support for filling the buffer with enough room to peek the next x characters to confirm it is the new line or delimiter instead of relying on just checking the first character. This fill behavior and peeking ahead will only be used if either the newline or delimiter is over two characters long.