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

fix #232 #234

Merged
merged 4 commits into from
Dec 5, 2024
Merged

fix #232 #234

merged 4 commits into from
Dec 5, 2024

Conversation

cmazakas
Copy link
Member

I wasn't exactly sure how to organize the tests or how much I should cover.

If you'd like, @jzmaddock , I can close this PR and I can instead open a new one with much more comprehensive test coverage for the match flags a user can pass in.

#else
throw e;
#endif
BOOST_REGEX_DETAIL_THROW("Invalid regular expression object");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally this should still throw a std::invalid_argument, otherwise we're breaking the interface?

@jzmaddock
Copy link
Collaborator

Apart from my tiny comment above, this all looks good to me: thanks Christian!

Credit to OSS-Fuzz for finding the problematic test regexes and configurations.
@jzmaddock
Copy link
Collaborator

If you'd like, @jzmaddock , I can close this PR and I can instead open a new one with much more comprehensive test coverage for the match flags a user can pass in.

We might as well get this in and then add that later?

@jzmaddock jzmaddock merged commit 0cbaa4e into boostorg:develop Dec 5, 2024
38 checks passed
@cmazakas cmazakas deleted the feature/fix-232 branch December 5, 2024 19:30
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.

2 participants