Fix the parsing logic of matches_pattern!
to support _
at the top level in top-level structs.
#627
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.
Fix the parsing logic of
matches_pattern!
to support_
at the top level in top-level structs.In the current parsing logic, the
_
field in patternSome(_)
is parsed asNone
, and as a result no FieldMatcher is generated, and the internalis()
matcher only evaluates the innerMatcher(the field_matcher).We add
pattern_only()
matcher for the case when field_matcher is empty and skip theis()
wrapping.Toward #626