-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Allow let_unit_value
in more cases
#9056
Conversation
r? @llogiq (rust-highfive has picked a reviewer for you, use r? to override) |
aa00e5b
to
d773ce0
Compare
Thank you! @bors r+ |
📌 Commit d773ce0 has been approved by |
d773ce0
to
a7d8f24
Compare
☔ The latest upstream changes (presumably #8666) made this pull request unmergeable. Please resolve the merge conflicts. |
a7d8f24
to
68c4fee
Compare
☔ The latest upstream changes (presumably #9082) made this pull request unmergeable. Please resolve the merge conflicts. |
* View through locals in `let_unit_value` when determining if inference is required * Don't remove typed let bindings for more functions
Ping @llogiq. I don't remember if I changed anything since you last checked this. |
In any case, this looks good. @bors r+ |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
The `let_unit_value` lint is new in Rust 1.62. rust-lang/rust-clippy#9056 might quiet it next release, though, so this may or may not be worth doing.
fixes #8998
changelog: Lint
let_unit_value
less aggressively when the type is specified