8000 Fix clippy warnings by dmaahs2017 · Pull Request #188 · tealdeer-rs/tealdeer · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fix clippy warnings #188

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

Merged
merged 4 commits into from
May 11, 2021
Merged

Fix clippy warnings #188

merged 4 commits 8000 into from
May 11, 2021

Conversation

dmaahs2017
Copy link
Contributor
  • allow struct excessive bools for Args struct.
  • change tests to use write_all instead of write
  • allow dead_code for the ConvigVar variant of PathSource

  - allow struct excessive bools for Args struct.
  - change tests to use write_all instead of write
  - allow dead_code for the ConvigVar variant of PathSource
@dmaahs2017
Copy link
Contributor Author
dmaahs2017 commented May 10, 2021

@niklasmohrin review please :)

this just fixes clippy --all-targets warnings. They were bothering me.

I wasn't sure if there was a reason for the ConfgVar variant in the PathSource enum. Presumably we will use it in the future. So for now I #allow(dead_code) for it. Otherwise I can just as easily delete it.

Edit: annoyingly the CI clippy check doesn't like the #allow[struct_excessive_bools) annotation, even though it works on my machine fine (Stable toolchain as well as nightly toolchain)

Copy link
Collaborator
@dbrgn dbrgn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dmaahs2017 the problem with the "excessive bools" lint is that the clippy version in CI does not know that lint yet. Right now we're testing with 1.51.0. Feel free to update that version in the CI config for the clippy job to the latest stable (1.52.0)!

Copy link
Collaborator
@niklasmohrin niklasmohrin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can only agree with @dbrgn, comment seems like a good idea and feel free to bump the rust version in .github/workflows/ci.yaml. Other than that, there's nothing to complain about. Good catch with write_all!

@dbrgn Why do we have MSRV anyway? It's not like we're a library that people depend on, so does it even matter? We could just say "builds on stable, everything else no guarantees"

@dmaahs2017
Copy link
Contributor Author

Can only agree with @dbrgn, comment seems like a good idea and feel free to bump the rust version in .github/workflows/ci.yaml. Other than that, there's nothing to complain about. Good catch with write_all!

@dbrgn Why do we have MSRV anyway? It's not like we're a library that people depend on, so does it even matter? We could just say "builds on stable, everything else no guarantees"

I'm curious why we run our tests on 1.41.1 as well as on stable

@dmaahs2017 dmaahs2017 force-pushed the fix-clippy-warnings branch from eb8795f to b9fcc6f Compare May 11, 2021 06:13
@niklasmohrin
Copy link
Collaborator

@dmaahs2017 FYI, further steps with MSRV are currently discussed in #190

@dbrgn dbrgn merged commit 4d4c7b6 into tealdeer-rs:master May 11, 2021
@dmaahs2017 dmaahs2017 deleted the fix-clippy-warnings branch May 11, 2021 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0