fix: KMP fallback branch updating matchStart with wrong matchPos value#1
Open
cesco69 wants to merge 1 commit intoalmost:masterfrom
Open
fix: KMP fallback branch updating matchStart with wrong matchPos value#1cesco69 wants to merge 1 commit intoalmost:masterfrom
cesco69 wants to merge 1 commit intoalmost:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The KMP fallback branch in the transform function updated matchPos before using its old value to compute matchStart, causing incorrect match positioning when the search pattern has overlapping prefixes and input is split across chunks.
This went unnoticed because existing tests only exercised this path with single-chunk input. Added regression tests that split overlapping-prefix patterns across multiple writes, which fail without the fix.