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

Resolve clippy warnings #1759

Merged
merged 1 commit into from Feb 8, 2023
Merged

Resolve clippy warnings #1759

merged 1 commit into from Feb 8, 2023

Conversation

ttytm
Copy link
Contributor

@ttytm ttytm commented Feb 4, 2023

What kind of change does this PR introduce?

  • Codestyle
  • Refactor

Fixes all the fluff generated by Clippy. Since there are so few warnings, imho it is best to just fix them, regardless of whether they are all important to neovide.

This will allow to extend the workflows to get more expressive reporting of clippy warnings and thus better detect shortcomings and improve overall code quality.

Did this PR introduce a breaking change?

A breaking change includes anything that breaks backwards compatibility either at compile or run time.

  • No

@MultisampledNight MultisampledNight merged commit 33856a5 into neovide:main Feb 8, 2023
@MultisampledNight
Copy link
Contributor

Thank you!

MultisampledNight added a commit that referenced this pull request Feb 9, 2023
Expands #1759. I don't know why the PR didn't contain everything, but
here we go.
@ttytm
Copy link
Contributor Author

ttytm commented Feb 9, 2023

Thank you! I should have also compared with the CI warnings and make sure my clippy is up to date.
It was only the warnings that was my local clippy(v0.1.65 at that time) was complaining about.

@ttytm ttytm deleted the resolve-clippy-warnings branch February 9, 2023 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants