Skip to content

feat: add RegexpCompiler option for custom regexp engines#73

Open
satisataka wants to merge 1 commit intogoogle:mainfrom
satisataka:feat/regexp-compiler
Open

feat: add RegexpCompiler option for custom regexp engines#73
satisataka wants to merge 1 commit intogoogle:mainfrom
satisataka:feat/regexp-compiler

Conversation

@satisataka
Copy link
Copy Markdown

Allow users to provide a custom regexp compiler via ResolveOptions.RegexpCompiler for PCRE-compatible features like lookahead that Go's regexp package does not support.

The Regexp interface requires only MatchString(string) bool, matching both regexp.Regexp and regexp2/compat.Regexp signatures.

Fixes #72

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Apr 28, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Allow users to provide a custom regexp compiler via ResolveOptions.RegexpCompiler
for PCRE-compatible features like lookahead that Go's regexp package does not support.

The Regexp interface requires only MatchString(string) bool, matching both
regexp.Regexp and regexp2/compat.Regexp signatures.

Fixes google#72
@satisataka satisataka force-pushed the feat/regexp-compiler branch from a76cce9 to 253af7b Compare April 28, 2026 11:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: allow custom regexp engine via RegexpCompiler option

1 participant