-
Notifications
You must be signed in to change notification settings - Fork 61
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
integration_test: Clear clippy warnings #121
Conversation
Last patch is interesting. The code in question is unsound. May be worth filing a compiler bug showing that the Meanwhile, we should replace this |
Looks like bitcoincore-rpc, where we copied this from, now just uses |
I propose:
Then I think we should get green CI on all three. |
Thanks for putting some time into this pile of PRs - I'll have a ago at your suggestion week (its the weekend now for me). |
0f46dcd
to
b45a071
Compare
clippy emits various warnigs of type: warning: unneeded `return` statement As suggested, remove unnecessary return statement.
clippy emits various warnings of form: warning: useless conversion to the same type: `&str` As suggested, remove the call to `into()`.
clippy emits various warnings of form: warning: empty string literal in `println!` As suggested, remove the double quotes.
Clippy emits: warning: use of `expect` followed by a function call As suggested, use `unwrap_or_else` instead.
Bump please. |
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.
ACK ac3fa84
Clear all the
clippy
warnings from theintegration_test
crate. Done in preparation for re-writing CI to use the newrun_task
script. The last patch is bodgy.