While I love what
cargo fix and
cargo fmt are providing with linting, we can all agree that sometimes linters are wrong. Currently, both utilities only have two modes of operation, the default “fix-all” and the more passive “check”. This doesn’t provide a lot of flexibility for the end-user, and this means that the implementers of
cargo fix have been a lot more careful with the compiler warnings/suggestions that they choose to distinguish as applicable.
I think an “interactive” option would be a great middleground between the two because it can accept human input for each decision. The human could pick from a set of options that could be even more flexible than a simple yes/no question; for example, I would love to see an “ignore”/“allow” option that automatically adds the proper
#[allow()] attribute to suppress the warning in future runs.