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``
35 lines
815 B
Rust
35 lines
815 B
Rust
//@ revisions: min_exhaustive_patterns exhaustive_patterns
|
|
|
|
// The precise semantics of inhabitedness with respect to unions and references is currently
|
|
// undecided. This test file currently checks a conservative choice.
|
|
|
|
#![cfg_attr(exhaustive_patterns, feature(exhaustive_patterns))]
|
|
#![cfg_attr(min_exhaustive_patterns, feature(min_exhaustive_patterns))]
|
|
#![feature(never_type)]
|
|
#![allow(dead_code)]
|
|
#![allow(unreachable_code)]
|
|
|
|
pub union Foo {
|
|
foo: !,
|
|
}
|
|
|
|
fn uninhab_ref() -> &'static ! {
|
|
unimplemented!()
|
|
}
|
|
|
|
fn uninhab_union() -> Foo {
|
|
unimplemented!()
|
|
}
|
|
|
|
fn match_on_uninhab() {
|
|
match uninhab_ref() {
|
|
//~^ ERROR non-exhaustive patterns: type `&!` is non-empty
|
|
}
|
|
|
|
match uninhab_union() {
|
|
//~^ ERROR non-exhaustive patterns: type `Foo` is non-empty
|
|
}
|
|
}
|
|
|
|
fn main() {}
|