-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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: dogfood Cargo -Zlints
table feature
#12178
Conversation
r? @ehuss (rustbot has picked a reviewer for you, use r? to override) |
|
||
[workspace.lints.clippy] | ||
all = { level = "allow", priority = -1 } | ||
disallowed_methods = "warn" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm assuming we'll either
- Need to find a way to make the clippy config only apply to the cargo package
- Only use this on the
cargo
lib (via an attribute)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The second one seems easier, though I assume most cargo-*
crates should follow the same rule of disallowed_methods
(if we split more subcrates…).
Just checking in to make sure this isn't waiting on me. This was marked as a Draft, but I'm not clear what's blocking or needs to be done. |
I am not sure if we want to move on.
|
There is a false positive in `src/bin/cargo/commands/build.rs`
9ea575f
to
91a812a
Compare
This is ready for review 🚀 |
This also remove `RUSTFLAGS: -D warnings` for test, as it seems to be redundant and clippy covers everythings
91a812a
to
e2f5925
Compare
@bors r+ Thanks! |
chore: dogfood Cargo `-Zlints` table feature
💔 Test failed - checks-actions |
The failure was caused by a crates.io deployment. It's being rolled back, see this Zulip comment. |
@bors retry |
clearly this was all a plot to get my two PRs processed earlier in the queue... 😂 |
☀️ Test successful - checks-actions |
Update cargo 11 commits in 2c03e0e2dcd05dd064fcf10cc1050d342eaf67e3..9765a449d9b7341c2b49b88da41c2268ea599720 2023-11-16 04:21:44 +0000 to 2023-11-17 20:58:23 +0000 - refactor(toml): Clean up workspace inheritance (rust-lang/cargo#12971) - docs: Recommend a wider selection of libsecret-compatible password managers (rust-lang/cargo#12993) - feat(cli): add color output for `cargo --list` (rust-lang/cargo#12992) - refactor: log when loading config from file (rust-lang/cargo#12991) - Link to rustc lint levels (rust-lang/cargo#12990) - chore(ci): Catch naive use of AtomicU64 early (rust-lang/cargo#12988) - cargo-credential-1password: Add missing `--account` argument to `op signin` command (rust-lang/cargo#12985) - chore: dogfood Cargo `-Zlints` table feature (rust-lang/cargo#12178) - cargo-credential-1password: Fix README (rust-lang/cargo#12986) - Fix a rustflags test using a wrong buildfile name (rust-lang/cargo#12987) - Fix some test output validation. (rust-lang/cargo#12982) r? ghost
What does this PR try to resolve?
-Zlints
unstable feature just landed onnightly-2023-05-25
(rustc 1.71.0-nightly). It would be awesome if Cargo starts dogfooding itself.How should we test and review this PR?
A shell script is added to check lint rules on nightly channel. This is expected to fail at this time. We probably want to fix lint errors in this PR or in follow-ups, depending on the review.
This does nothing on stable channel, which Cargo sticks to. Merely that
cargo build
becomes noisy because-Zlints
triggers lots ofunused manifest key: lints
warnings, and has no way to turn them off. If people feel unease about this, we can wait.Additional information