-
Notifications
You must be signed in to change notification settings - Fork 219
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: use standard lint settings and fix lints #4066
chore: use standard lint settings and fix lints #4066
Conversation
2a79468
to
3c285fd
Compare
5a96d58
to
d6cfb6d
Compare
@SWvheerden @deniskolodin Can I have a review on this one? It may be easier to check each of the commits individually. |
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.
This looks good.
The only thing I think we need to add is todo's and a good first issue in github so we can tackle some of these large functions. We have way too many of them.
@SWvheerden definitely agree, the intention here was to mark them so that they can be fixed later. Searching for too_many_lines should do it so don't think we need a Todo above each of them. |
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.
It's pretty huge, but I haven't serious admonitions here
Description
Motivation and Context
Tari repo uses standard linter settings EDIT: there are too many cast clippys to investigate, so that is left for another PR
Larger fixes are in #4063 #4064 #4065 which should be merged before this PR.
How Has This Been Tested?
cargo lints clippy
passes