-
Notifications
You must be signed in to change notification settings - Fork 3
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
Clippy #102
Conversation
As I understand it, we get warns for dead code because we're _only_ using the fields here via their Debug-instances (eg. for logs) Since we're actually just-fine-thank-you-very-much with the autogenerated strings, this seems needlessly strict to us and creating custom Display-instances just to squelch this seems even noisier than allowing the dead_code fields.
Need help with the remaining failures (run |
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.
Some are a bit nit picky, and shouldn't be considered blocking
I wasn't sure how to best show solving the last clippy lints without having something to point at so I made a commit 0f9367c and added some GitHub comments. I hope that's somewhat useful. It did get hit with a rust fmt which makes the diff unnecessarily large, but I've pointed at the parts of the code that were changed, and tried to show why clippy didn't give great hints (clippy didn't fully know to explain what the changes meant for the impl's using the trait) |
Thanks for the help, think I've incorporated it all (and dropped the formatting for now so we don't mix that up in this already-large diff) |
A few clippy hints remain that I don't know how to deal with, need a hand