Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support matching binary utf8 bytes #130

Merged
merged 2 commits into from
Mar 8, 2021
Merged

Support matching binary utf8 bytes #130

merged 2 commits into from
Mar 8, 2021

Conversation

jc4x4
Copy link
Contributor

@jc4x4 jc4x4 commented Feb 22, 2021

Summary:

  1. Introduce MatcherInput to represent both utf16 and utf8.
  2. Reuse existing tests with ApiTestUtils to use both MatcherInput.
  3. Updated some benchmark to use binary. Didn't find any meaningful difference.

Closes #84

@google-cla google-cla bot added the cla: yes label Feb 22, 2021
Summary:
1. Introduce MatcherInput to represent both utf16 and utf8.
2. Reuse existing tests with ApiTestUtils to use both MatcherInput.
Found no meaningful difference between binary vs string.
@steveniemitz
Copy link

ah this is awesome! Any chance of getting a new version of re2j published?

@sjamesr
Copy link
Contributor

sjamesr commented Mar 8, 2021

I'll do that now

@steveniemitz
Copy link

hm, just gave this a try. It looks like it's missing support for the \C escape sequence. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for binary-mode matching?
3 participants