You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/inside-rust/this-development-cycle-in-cargo-1.90.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ and adopting of new lints in a code base.
64
64
However, `cargo fix`
65
65
- Can be slow ([#13214](https://github.com/rust-lang/cargo/issues/13214))
66
66
- Only applies a subset of possible lints
67
-
-You can't be selective of which lints are fixed without a lot of mucking with `RUSTFLAGS` which was important with the 2024 Edition migration because some lints still had a lot of false positives at first
67
+
-Can't be selective of which lints are fixed without a lot of mucking with `RUSTFLAGS` which was important with the 2024 Edition migration because some lints still had a lot of false positives at first
68
68
69
69
A problem with addressing these is the current architecture.
70
70
`cargo fix` is implemented as a variant of `cargo check` that replaces `rustc` with `cargo` being run in a special mode that will call `rustc` in a loop, applying fixes until there are none.
0 commit comments