RegexMatcher: Pattern always require full string match #35
Due to wrongly non-matching regex patterns, I noticed an abnormal and inefficient behavior of the current implementation of regex() function: The pattern always has to match on the full string value to return true instead of matching on substrings (next match).
This contradicts standard regex implementations, leads to unnecessary regex state machine steps (especially for leading greedy
Reason: RegexMatch.evaluate() uses java.util.regex.Matcher.matches() instead of next-match find(). Also check out this discussion on the differences.
Steps to reproduce the problem
The text was updated successfully, but these errors were encountered: