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

Provide a more accurate count of max possible backtracks #445

Open
tjenkinson opened this issue Oct 21, 2023 · 0 comments
Open

Provide a more accurate count of max possible backtracks #445

tjenkinson opened this issue Oct 21, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@tjenkinson
Copy link
Owner

With ^(1|1|2|2)$ the tool will currently report 2 backtracks even though there can only be 1. This is because it doesn't check to see if the same input string could be used for both backtracks, which it can't.

^(1|1|2|2|[12])$ should result in 3.

Not sure how expensive this could be to calculate.

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

No branches or pull requests

1 participant