Ignore shadow
warns in code from macro expansions
#10697
Merged
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 PR fixes #9757
I am in doubt if just looking for
pat.span.from_expansion()
would be sufficient instead of looking for bothpat.span.desugaring_kind().is_some()
orpat.span.from_expansion()
. The tests (including the new one) passes if I leave onlyif pat.span.from_expansion()
. Any feedbacks?Also, this is my first PR here, sorry for anything and thanks for the patience!
changelog: [
shadow_same
,shadow_reuse
,shadow_unrelated
]: avoiding warns in macro-generated code