Skip to content

Fix clippy warnings #2065

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

Merged
merged 1 commit into from
Apr 16, 2025
Merged

Fix clippy warnings #2065

merged 1 commit into from
Apr 16, 2025

Conversation

senekor
Copy link
Contributor

@senekor senekor commented Apr 16, 2025

No description provided.

@senekor senekor requested a review from ellnix April 16, 2025 08:49
Copy link
Contributor

@ellnix ellnix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems strange that it's not just a vec![0; 36], but nothing wrong per se.

@senekor
Copy link
Contributor Author

senekor commented Apr 16, 2025

TBH I find this check annoying, the example solutions aren't shown to users. No need to keep them at 100% code quality. I'm just always too lazy to get rid of this check, fixing the warnings is easier in the moment.

@senekor senekor merged commit 9bc0745 into main Apr 16, 2025
12 checks passed
@senekor senekor deleted the senekor/omxxmtosluvq branch April 16, 2025 08:59
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.

2 participants