2018-08-30 07:18:55 -05:00
|
|
|
// run-pass
|
2018-10-16 10:07:41 -05:00
|
|
|
|
2020-12-28 11:15:16 -06:00
|
|
|
// This test is bogus (i.e., should be check-fail) during the period
|
2018-10-16 10:07:41 -05:00
|
|
|
// where #54986 is implemented and #54987 is *not* implemented. For
|
2019-04-22 02:40:08 -05:00
|
|
|
// now: just ignore it
|
2018-10-16 10:07:41 -05:00
|
|
|
//
|
2023-04-15 18:11:42 -05:00
|
|
|
// ignore-test (#54987)
|
2018-10-16 10:07:41 -05:00
|
|
|
|
|
|
|
// These are variants of issue-26996.rs. In all cases we are writing
|
|
|
|
// into a record field that has been moved out of, and ensuring that
|
|
|
|
// such a write won't overwrite the state of the thing it was moved
|
|
|
|
// into.
|
|
|
|
//
|
|
|
|
// That's a fine thing to test when this code is accepted by the
|
|
|
|
// compiler, and this code is being transcribed accordingly into
|
|
|
|
// the ui test issue-21232-partial-init-and-use.rs
|
|
|
|
|
2016-07-05 16:18:22 -05:00
|
|
|
fn main() {
|
|
|
|
let mut c = (1, (1, "".to_owned()));
|
|
|
|
match c {
|
|
|
|
c2 => { (c.1).0 = 2; assert_eq!((c2.1).0, 1); }
|
|
|
|
}
|
|
|
|
|
|
|
|
let mut c = (1, (1, (1, "".to_owned())));
|
|
|
|
match c.1 {
|
|
|
|
c2 => { ((c.1).1).0 = 3; assert_eq!((c2.1).0, 1); }
|
|
|
|
}
|
|
|
|
}
|