-
Notifications
You must be signed in to change notification settings - Fork 168
Enable clippy in CI #174
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
Enable clippy in CI #174
Conversation
r? @thejpster (rust_highfive has picked a reviewer for you, use r? to override) |
da2a5e9
to
cbd9389
Compare
I think this issue ties a back to (and extends) our original discussion on enabling code style checks as well (can't find the issue right now...). |
The main reason I'd like Clippy in CI here, is so |
a3d2bd5
to
fed3855
Compare
Happy to start with clippy, and add |
bors r+ |
174: Enable clippy in CI r=thejpster a=m-ou-se Co-authored-by: Mara Bos <[email protected]>
Build failed |
Er, how do we find out why bors is sad? |
Sometimes the |
Build failed due to network error, I've retriggered a rebuild to make sure (unfortunately I hit the wrong button so it's not just retrying the one job that had failed). |
bors retry |
174: Enable clippy in CI r=thejpster a=m-ou-se Co-authored-by: Mara Bos <[email protected]>
Hmm. Clicked all the little links and tiny buttons. Failed to see the great big blue link in the comment bors posted. Thanks! |
Build succeeded |
175: Enable the missing_inline_in_public_items clippy lint. r=jonas-schievink a=m-ou-se This adds `#![deny(clippy::missing_inline_in_public_items)]` to make sure all functions in this crate are marked `#[inline]`, unless they are explicitly marked with `#[allow(clippy::missing_inline_in_public_items)]`. Only three functions in this crate are not `#[inline]`: - `write_words` - `write_all` - `write_aligned` Additionally, the derived `Debug` impl's also have a non-inline implementations. This unfortunately means that the allow attribute also needs to added to any types deriving `Debug`. See also #171 and #174 (comment). Co-authored-by: Mara Bos <[email protected]>
No description provided.