fadabd6fbb
This commit is just covering the feature gate itself and the tests that made direct use of `!` and thus need to opt back into the feature. A follow on commit brings back the other change that motivates the revert: Namely, going back to the old rules for falling back to `()`.
31 lines
899 B
Rust
31 lines
899 B
Rust
// Copyright 2017 The Rust Project Developers. See the COPYRIGHT
|
|
// file at the top-level directory of this distribution and at
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
// option. This file may not be copied, modified, or distributed
|
|
// except according to those terms.
|
|
|
|
#![feature(never_type)]
|
|
#![feature(exhaustive_patterns)]
|
|
|
|
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,
|
|
..
|
|
}) => {}
|
|
}
|
|
}
|