{{ message }}
<regex>: Avoid allocating during matching when regex defines no captures#5518
Merged
StephanTLavavej merged 1 commit intoMay 22, 2025
Conversation
StephanTLavavej
added
performance
StephanTLavavej
approved these changes
May 20, 2025
Closed
Member
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
Member
muellerj2
deleted the
regex-no-allocations-during-matching-of-regexes-without-captures
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is no need to allocate the capture group vectors in the matcher state when the only capture group is 0, because capture group 0 is just the whole match and we already know the bounds of the whole match (start is the position where
_Matcher2::_Matchwas called, end is the value of_Curin the matcher state).I can't come up with any additional test cases that should be added for this change and I think the existing test coverage should already catch it if I made a mistake here.
Benchmark on my machine: