Fix GlobPrefix. #220
Merged
Fix GlobPrefix. #220
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.
Due to a misunderstanding from my part,
GlobPrefixwould happily return a literal prefix that must start any match, but would not take care to anchor that match at the start of the string, which made it unsuitable to take advantage of the LIKE optimization, and just wrong.Unfortunately package
regexpdoes not offer a suitable API for this; had to usesyntax/regexpinstead.Significant fuzzing went into validating the solution.
This is a breaking API change.