-
-
Notifications
You must be signed in to change notification settings - Fork 809
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
chore: Fix errors reported by clippy beta #18286
Conversation
There are a few more with |
Whoops, I forgot to push ;) |
Another one... :)
|
9fad19e
to
b593d88
Compare
They just won't run out... 😅 |
6833fad
to
e8390a0
Compare
About the (current) second commit: rust-lang/rust-clippy#12917 may be related. |
To be honest, we should have just commented out that doc comment. It does not apply to anything as the original code has been commented out too. |
Yeah, but nobody suggested it until now, and even when I saw at first what you did now, it struck me as really weird; but given that "doc comments" are almost like proper language elements in Rust, it does make some weird sense to "actually comment them out", now that I think about it... |
4432831
to
6c32ee8
Compare
Holy mother of wide-reaching nit diffs, Crabman! |
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.
LGTM, thank you! 🎉
I guess this is better merged sooner rather than later, so it doesn't start bitrotting on us...
|
That stray |
Seems like someone forgot to remove it, it does not apply to anything.
Doc comments which are not attached to any code (e.g.. the code has been commented out) need to be commented out, otherwise they may apply to the next item below it.
This fixes errors like error: the following explicit lifetimes could be elided: 'a error: empty line after doc comment error: unneeded `return` statement
This fixes errors like
Plus others related to doc comments.