docs: clarify Captures::len includes non-matching captures #832
Conversation
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
BurntSushi
approved these changes
Jul 5, 2022
BurntSushi
requested changes
Jul 5, 2022
Member
BurntSushi
left a comment
BurntSushi
left a comment
There was a problem hiding this comment.
Can you make the same change to re_bytes.rs as well?
Member
|
Nevermind, I'll make the change and include it in a rollup. |
BurntSushi
pushed a commit
that referenced
this pull request
Jul 5, 2022
We do the same for CaptureLocations too. Closes #832
This was referenced Oct 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This caught me out: mentally I map "captured groups" to the successful captures; capture groups that didn't capture anything weren't "captured." I understand why the function returns what it does in retrospect, but hopefully this can help someone else.