Allow clippy's new assertions-on-constants lint
What the developer wrote
Authored by Matt Corallo
Allow clippy's new assertions-on-constants lint
This is really dumb, `assert!(cfg!(fuzzing))` is a perfectly
reasonable thing to write!
What changed, and why it matters
This commit only adds one line to a shell script used in continuous integration. It tells the Clippy code-analysis tool to ignore a newly introduced lint about assertions on constant values. The change does not modify any actual Rust source code, runtime behavior, or security-sensitive logic.
No security action needed. This is a lint/CI configuration change with no product impact.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds -A clippy::assertions-on-constants to ci/check-lint.sh, which is the CI script that runs Clippy lints. This suppresses Clippy’s warning for patterns like assert!(cfg!(fuzzing)). No Rust source files were changed, and no program logic, API, or cryptographic code is affected.
Changed components
ci/check-lint.shInspect captured patch +1 / −0
diff --git a/ci/check-lint.sh b/ci/check-lint.sh
index c1f1b08..c072426 100755
--- a/ci/check-lint.sh
+++ b/ci/check-lint.sh
@@ -13,6 +13,7 @@ CLIPPY() {
-A clippy::unwrap-or-default \
-A clippy::upper_case_acronyms \
-A clippy::swap-with-temporary \
+ -A clippy::assertions-on-constants \
`# Things where we do odd stuff on purpose ` \
-A clippy::unusual_byte_groupings \
-A clippy::unit_arg \
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.