Repository navigation
RegularParser now finds tags inside runs of opening tags - #133
Merged
Merged
Conversation
thunderer
force-pushed
the
tk-regular-overlap
branch
from
November 8, 2026 14:17
2a76ff1 to
3a7533e
Compare
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
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.
With a syntax whose opening tag overlaps itself (
[[,{{,<<),RegularParsermissed tags that follow a run of opening-tag characters. Its lexer cut the run into opening tags from the left, so with[[it foundain[[[[a]]but not in[[[a]], where the odd[stuck to the name.HybridParserandRegexParserfindaat offset 1, the same way every parser finds[a]in[[a]with the default syntax.[!,<!--,{%) keep the same output,[[a]]x[[[//a]]givesawith contentx[, asHybridParserdoes,RegularParserandHybridParsernow give the same output on 13 syntaxes in a differential test of 20000-40000 random inputs each, and the new data-provider test checks both parsers on 8 cases,