diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-05-09 19:09:31 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-09 19:09:31 +0200 |
| commit | 779fe95298c60eab447ba02254e41796d66c2971 (patch) | |
| tree | 83118dbeae75abf57489a5f950a813660eaf3b1c /compiler/rustc_errors/src/json.rs | |
| parent | a40fa8f443759c23827ec46c40a047375021ae1f (diff) | |
| parent | 3c5255391232dab1a6a5764be671dbd5315fe81e (diff) | |
| download | rust-779fe95298c60eab447ba02254e41796d66c2971.tar.gz rust-779fe95298c60eab447ba02254e41796d66c2971.zip | |
Rollup merge of #124926 - Alexendoo:feature-maybe-incorrect, r=est31
Make `#![feature]` suggestion MaybeIncorrect Fixes https://github.com/rust-lang/rust-clippy/issues/12784 The `unstable_name_collisions` lint uses `disabled_nightly_features` to mention the feature name, but accepting the suggestion would result in an ambiguity error There are other calls where accepting the feature gate would fix code when ran with `cargo fix --broken-code`, though it's not always desirable to add a feature gate even if the user is currently on nightly so MaybeIncorrect seems appropriate
Diffstat (limited to 'compiler/rustc_errors/src/json.rs')
0 files changed, 0 insertions, 0 deletions