swarm repositories / source
aboutsummaryrefslogtreecommitdiff
path: root/docs/rust-linting-proposal.md
diff options
context:
space:
mode:
authormain <main@swarm.moe>2026-04-04 21:50:22 -0400
committermain <main@swarm.moe>2026-04-04 21:50:22 -0400
commit8048d67e5917b771be9aa819094aebf3936d0e98 (patch)
tree467090c90a5f263088a1de701095a040c66733ff /docs/rust-linting-proposal.md
parent4053cb24991c406e53dd04a015ba5dd44c6620f3 (diff)
downloadrust_starter-8048d67e5917b771be9aa819094aebf3936d0e98.zip
docs: manifest-own warning fatality
Diffstat (limited to 'docs/rust-linting-proposal.md')
-rw-r--r--docs/rust-linting-proposal.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/rust-linting-proposal.md b/docs/rust-linting-proposal.md
index 53b9ae2..88e5612 100644
--- a/docs/rust-linting-proposal.md
+++ b/docs/rust-linting-proposal.md
@@ -22,6 +22,10 @@ One extra local fact matters: there is effectively no checked-in Rust CI posture
One more distinction matters: Clippy’s `too_many_lines` is about function bodies, not whole source files. If the goal is to force large modules to split, the starter pack needs an explicit file-level check instead of pretending the existing lint already covers it.
+One more ratchet should be explicit: if the repo wants warnings to be fatal, that belongs in
+`[workspace.lints.rust]` as `warnings = "deny"`, not in runner-side `cargo clippy -- -D warnings`
+tails. The manifest owns policy; the runner merely executes it.
+
## Local Survey
### The old shape
@@ -194,6 +198,7 @@ rust-version = "1.xx"
version = "0.1.0"
[workspace.lints.rust]
+warnings = "deny"
elided_lifetimes_in_paths = "deny"
unexpected_cfgs = "deny"
unsafe_code = "deny"