Ignore synthetic type parameters for extra_unused_type_parameters#10338
Conversation
extra_unused_type_parameters.extra_unused_type_parameters
2e208ba to
b522965
Compare
|
@bors r+ Thanks! (Let's hope this doesn't conflict with the other PR) |
|
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message |
|
☔ The latest upstream changes (presumably #10321) made this pull request unmergeable. Please resolve the merge conflicts. |
b522965 to
f6b292b
Compare
f6b292b to
1ee4651
Compare
|
Sorry about that - conflicts should be resolved now @flip1995 |
|
No worries! Thanks for resolving them so quickly. @bors r+ |
|
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
There was a minor bug around calculating spans when forming the help message. An example:
In this case, the entire list of generics should be highlighted, instead of each individual parameter. The culprit is the
impl Default, which registers as a type parameter but doesn't live within the<...>. Because synthetic parameters can't ever be manually created, we just ignore them for this lint.r? @flip1995
changelog: none