Skip to content
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

Explore clippy rules and apply quality of life recommendations #193

Closed
ebuchman opened this issue Mar 28, 2020 · 3 comments · Fixed by #868
Closed

Explore clippy rules and apply quality of life recommendations #193

ebuchman opened this issue Mar 28, 2020 · 3 comments · Fixed by #868
Labels
ci Related to continuous integration code-quality Issues relating to linting configuration and general code quality needs-dod Needs a "definition of done" for clarity

Comments

@ebuchman
Copy link
Member

This is an issue to track the work started in #122 cc @xla

@ebuchman ebuchman added the structure High level repo-wide structural concerns label Jun 3, 2020
@liamsi
Copy link
Member

liamsi commented Jun 4, 2020

It seems like in the change from circleci to github actions clippy is called in a less strict way than perviously. If I run it locally via:
cargo clippy --all --all-targets -- -Dwarnings -Drust-2018-idioms it often shows some errs that do not show up in CI. Would be good to start with this simple online change.

@xla xla added the ci Related to continuous integration label Jul 4, 2020
@thanethomson thanethomson added code-quality Issues relating to linting configuration and general code quality and removed structure High level repo-wide structural concerns labels Mar 22, 2021
@thanethomson
Copy link
Contributor

Is the goal here to effectively apply as many of the clippy::pedantic rules as possible?

And what's the "definition of done" for this issue? It seems a little vague.

@thanethomson thanethomson added the needs-dod Needs a "definition of done" for clarity label Mar 22, 2021
@greg-szabo
Copy link
Member

Definition of done, based on the issue: turn all clippy warnings into errors.

I understand that there's an underlying bigger work that happened here previously (to apply as many clippy rules as we can) but I don't see this work progressing forward right now and half-defined issues won't help it either.

I propose we close this issue when we close #406 and if/when we feel the need to improve our clippy settings again, open an issue with well-defined targets.

@greg-szabo greg-szabo mentioned this issue Apr 22, 2021
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Related to continuous integration code-quality Issues relating to linting configuration and general code quality needs-dod Needs a "definition of done" for clarity
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants