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

Edge case of (*ACCEPT) + endanchored fix #357

Open
addisoncrump opened this issue Dec 8, 2023 · 2 comments
Open

Edge case of (*ACCEPT) + endanchored fix #357

addisoncrump opened this issue Dec 8, 2023 · 2 comments
Labels
JIT Relating to the JIT feature

Comments

@addisoncrump
Copy link
Contributor

Related to #353.

  re> /(*ACCEPT)*a/endanchored
data> a\=notempty
No match
data> a\=notempty,no_jit
 0: a
@PhilipHazel
Copy link
Collaborator

There are always going to be edge cases like this where JIT and the interpreter differ, just as there are similar sorts of things where PCRE2 and Perl differ (see pcre2compat). I am not at all sure it is worth trying to find "fixes" for every one of them.

@addisoncrump
Copy link
Contributor Author

I understand. Bringing them into alignment, however, will allow the fuzzer to effectively instantly find errors in new features that can then be used in regression testing.

@NWilson NWilson added the JIT Relating to the JIT feature label Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
JIT Relating to the JIT feature
Projects
None yet
Development

No branches or pull requests

3 participants