diff options
| author | Philipp Krones <hello@philkrones.com> | 2020-06-23 14:39:42 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-23 14:39:42 +0200 |
| commit | 1f39eeb06d3be2f565a5e9105339fb0feb366173 (patch) | |
| tree | 5bb92ef086cd741fb51e8a471fc9c3ecd407a0e0 /src | |
| parent | 7c61be615a10cc4dd3ed1b9b1692511a9221c8f8 (diff) | |
| parent | 56f25e3e62dbdd8f84a9152bbfb73a35055363dd (diff) | |
| download | rust-1f39eeb06d3be2f565a5e9105339fb0feb366173.tar.gz rust-1f39eeb06d3be2f565a5e9105339fb0feb366173.zip | |
Rollup merge of #5705 - dtolnay:orpat, r=flip1995
Downgrade unnested_or_patterns to pedantic Even with #5704 fixed, I don't believe it is a safe bet that if someone is using or-patterns anywhere in a codebase then they want to use it as much as possible in the whole codebase. I think it would be reasonable to reevaluate after the feature is stable. I feel that a warn-by-default lint suggesting use of an unstable feature, even if already being used in one place, is questionable. changelog: Remove unnested_or_patterns from default set of enabled lints
Diffstat (limited to 'src')
| -rw-r--r-- | src/lintlist/mod.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lintlist/mod.rs b/src/lintlist/mod.rs index cac3cc6bdb3..edceb755180 100644 --- a/src/lintlist/mod.rs +++ b/src/lintlist/mod.rs @@ -2329,7 +2329,7 @@ pub static ref ALL_LINTS: Vec<Lint> = vec![ }, Lint { name: "unnested_or_patterns", - group: "complexity", + group: "pedantic", desc: "unnested or-patterns, e.g., `Foo(Bar) | Foo(Baz) instead of `Foo(Bar | Baz)`", deprecation: None, module: "unnested_or_patterns", |