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(clarity): Remove unused imports and enable warning #5660

Merged

Conversation

jbencin
Copy link
Contributor

@jbencin jbencin commented Jan 6, 2025

Description

Remove unused imports in clarity, and remove the line #![allow(unused_macros)] to enable unused import warnings for this crate

Additional info (benefits, drawbacks, caveats)

I've left #![allow(unused_macros)] on for src/vm/analysis/tests. This module is compiled with the condition #[cfg(any(test, feature = "testing"))], and it's the testing feature flag that causes the issue here, since most of the code is inside unit tests marked with #[test]. I don't want to mess with this now and risk breaking something that uses Clarity's testing feature

I've tested that clarity still builds with all feature flags found in Cargo.toml

@jbencin jbencin requested a review from a team as a code owner January 6, 2025 15:17
Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

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

Excellent!

@obycode obycode requested a review from a team January 10, 2025 22:21
@jbencin jbencin requested review from jferrant and jcnelson January 14, 2025 20:08
@jbencin jbencin added the lint Related to linting/clippy/cargo warns label Jan 21, 2025
@jbencin jbencin enabled auto-merge January 22, 2025 17:51
@jbencin jbencin added this pull request to the merge queue Jan 22, 2025
Merged via the queue into stacks-network:develop with commit 9cacb22 Jan 22, 2025
169 of 180 checks passed
@jbencin jbencin deleted the chore/remove-unused-imports-clarity branch January 22, 2025 21:02
@blockstack-devops
Copy link
Contributor

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Jan 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lint Related to linting/clippy/cargo warns locked
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants