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``
21 lines
566 B
Rust
21 lines
566 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)]
|
|
|
|
mod private {
|
|
pub struct Private {
|
|
_bot: !,
|
|
pub misc: bool,
|
|
}
|
|
pub const DATA: Option<Private> = None;
|
|
}
|
|
|
|
fn main() {
|
|
match private::DATA {
|
|
//~^ ERROR non-exhaustive patterns: `Some(Private { misc: true, .. })` not covered
|
|
None => {}
|
|
Some(private::Private { misc: false, .. }) => {}
|
|
}
|
|
}
|