Closed ehiggs closed 2 years ago
Hello @ehiggs
thanks for your PR!
bors try
Build succeeded:
Glad to help! @ManyTheFish let me know if there are any changes or explanations needed.
@ehiggs thanks for your PR. The team has a lot to do currently because of our sprint + hacktoberfest. We will do our best to review your PR asap 😄
Thanks again for your work, this is really appreciated
@ManyTheFish what is the best solution then? Which PRs can be problematic?
How do I set a label like "no breaking" for the Enforce PR labels?
However, it changes a significant amount of files and I'm a bit concerned by the merge conflicts that people will have. thinking
I understand the concern, which is why I only did some of the fixes. If someone needs help with rebasing, let me know and I can help.
I think we can merge this PR, There is not so much external contribution now, sorry @ehiggs for the time! Thank you for your contribution! 👍
bors merge
Build succeeded:
This message is sent automatically
Thank you for contributing to Meilisearch. If you are participating in Hacktoberfest, and you would like to receive some gift from Meilisearch too, please complete this form.
Related issue
No issue fixed. Simply cleaning up some code for clippy on the march towards a clean build when #659 is merged.
What does this PR do?
Most of these are calling clone when the struct supports Copy.
Many are using & and &mut on
self
when the function they are called from already has an immutable or mutable borrow so this isn't needed.I tried to stay away from actual changes or places where I'd have to name fresh variables.
PR checklist
Please check if your PR fulfills the following requirements: