Fix Bug [#14844] : Boyer-Moore bad character shift has no effect (for-loop variable reassignment)#14848
Open
Divyanshu-hash wants to merge 1 commit into
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
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.
Describe your change:
In
strings/boyer_moore_search.py, thebad_character_heuristic()method attempts to skip positions using the bad character rule, but the shift has no effect because it reassigns thefor-loop variablei. In Python, reassigning the loop variable inside aforloop does not change the iteration, meaning the algorithm was behaving as brute-force O(nm) instead of Boyer-Moore O(n/m).This PR fixes the bug by replacing the
forloop with awhileloop, allowing the shift to take effect. It also adds amax()guard to ensure the algorithm never shifts backwards, and expands the doctests to cover non-matching and overlapping edge cases.Checklist: