26cb6c7287
mark `min_exhaustive_patterns` as complete This is step 1 and 2 of my [proposal](https://github.com/rust-lang/rust/issues/119612#issuecomment-1918097361) to move `min_exhaustive_patterns` forward. The vast majority of in-tree use cases of `exhaustive_patterns` are covered by `min_exhaustive_patterns`. There are a few cases that still require `exhaustive_patterns` in tests and they're all behind references. r? ``@ghost``
27 lines
756 B
Rust
27 lines
756 B
Rust
//@ revisions: min_exhaustive_patterns exhaustive_patterns
|
|
#![cfg_attr(exhaustive_patterns, feature(exhaustive_patterns))]
|
|
#![cfg_attr(min_exhaustive_patterns, feature(min_exhaustive_patterns))]
|
|
#![feature(never_type)]
|
|
#![deny(unreachable_patterns)]
|
|
|
|
fn main() {}
|
|
|
|
fn foo(nevers: &[!]) {
|
|
match nevers {
|
|
//[min_exhaustive_patterns]~^ ERROR non-exhaustive patterns: `&[_, ..]` not covered
|
|
&[] => (),
|
|
};
|
|
|
|
match nevers {
|
|
&[] => (),
|
|
&[_] => (),
|
|
&[_, _, ..] => (),
|
|
};
|
|
|
|
match nevers {
|
|
//[exhaustive_patterns]~^ ERROR non-exhaustive patterns: `&[]` not covered
|
|
//[min_exhaustive_patterns]~^^ ERROR non-exhaustive patterns: `&[]` and `&[_, _, ..]` not covered
|
|
&[_] => (),
|
|
};
|
|
}
|