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

chore: clippy-lint the coapcore crate #377

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ROMemories
Copy link
Collaborator

@ROMemories ROMemories commented Aug 5, 2024

Description

  • Add the crate to the list of clippy-linted crates.
  • Fix clippy warnings.

Issues/PRs references

Depends on #376

Open Questions

None

Change checklist

  • I have cleaned up my commit history and squashed fixup commits.
  • I have followed the Coding Conventions.
  • I have performed a self-review of my own code.
  • I have made corresponding changes to the documentation.

@@ -130,6 +130,10 @@ impl<Crypto: lakers::Crypto> Default for SecContextState<Crypto> {
}

#[derive(Debug)]
#[expect(
clippy::large_enum_variant,
reason = "having no allocator, we cannot add a level of indirection"
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Can we do something about it or is my reason correct?

@ROMemories
Copy link
Collaborator Author

@chrysn I was careful when making the changes recommended by clippy, but could you still check them?

@ROMemories ROMemories requested a review from chrysn August 5, 2024 15:22
@ROMemories ROMemories marked this pull request as ready for review August 5, 2024 15:22
@ROMemories ROMemories added the CI label Aug 5, 2024
- Add the crate to the list of clippy-linted crates.
- Fix most of the warnings.
@chrysn
Copy link
Collaborator

chrysn commented Aug 20, 2024

If it's alright with you I'd rather apply those to #348 than merge them here; this would be very prone to merge conflicts.

@ROMemories ROMemories marked this pull request as draft August 20, 2024 07:58
@ROMemories
Copy link
Collaborator Author

If it's alright with you I'd rather apply those to #348 than merge them here; this would be very prone to merge conflicts.

Fine with me, marking this PR as draft for now; we'll close it without merging when #348 lands and includes these changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants