-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fix false positive on filter_next
#7562
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
Conversation
r? @xFrednet (rust-highfive has picked a reviewer for you, use r? to override) |
Seems like the docs is still suggesting to use I think it would be good if the docs explicitly explains why |
Oh, you're right. We should update that documentation, would you like to do that? 🙃 Diagnostic items in general are sadly not as good documented as they should. There is an issue for that in rust-lang/rustc-dev-guide#1188 to cover the entire topic. (I plan to work on it in the future when I have a bit more time again) |
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.
Looks good to me. Thank you for the fix! 🙃
If you would like to do it, it would be good to do it in another PR to also get general feedback on the documentation update. Having it in this PR could let it fly under the radar. @bors r+ |
📌 Commit 91b598a has been approved by |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Tweak common tool docs on type-implement-trait check See #7562 (comment). changelog: none
fixes #7561
changelog: Fix false positive on [
filter_next
] when a method does not implementIterator