Do not call skip parser if we are already in failed state in seq_parser #256

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.

Sign up for GitHub

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

Jump to bottom

Merged

tzlaine merged 1 commit into boostorg:develop from andreasbuhr:do_not_skip_on_failure_in_seq_parser

Oct 31, 2025

andreasbuhr commented Aug 2, 2025

Now this gave me more than 10% speedup.

Currently, the seq_parser calls the skip-parser for each child, even if we are already failed.


          Do not call skip parser if we are already in failed state in seq_parser

d49a1a2

tzlaine merged commit f7246de into boostorg:develop

1 check failed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet