-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add wildcard_let lint #12902
Add wildcard_let lint #12902
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @llogiq (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
/// this may be used by crates that with to force `#[must_use]` | ||
/// values to actually used, along with `#[forbid(unused_must_use)]`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this use-case not already covered by let_underscore_must_use
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the 5 years of #4090 being open, noone brought that lint up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I understand there is some overlap, but the wildcard_let lint is broader in scope, correct? In that case, the lint should at least check if the let_underscore_must_use
lint would apply and avoid linting in that case to avoid double messages.
☔ The latest upstream changes (presumably #12849) made this pull request unmergeable. Please resolve the merge conflicts. |
Hey @lolbinarycat , this is a ping from triage, since there hasn't been any activity in some time. Are you still planning to continue this implementation? If you have any questions, you're always welcome to ask them in this PR or on Zulip. @rustbot author |
@xFrednet not really, since the previously mentioned lint already covers it's usecase. |
Fixes #4090
changelog: [
wildcard_let
]: new restriction lint to forbid use oflet _