tests/ui/array-slice-vec/nested-vec-3.rs

   1 // run-pass
   2 // needs-unwind
   3 #![allow(overflowing_literals)]
   4
   5 // ignore-emscripten no threads support
   6
   7 // Test that using the `vec!` macro nested within itself works when
   8 // the contents implement Drop and we hit a panic in the middle of
   9 // construction.
  10
  11 use std::thread;
  12 use std::sync::atomic::{AtomicUsize, Ordering};
  13
  14 static LOG: AtomicUsize = AtomicUsize::new(0);
  15
  16 struct D(u8);
  17
  18 impl Drop for D {
  19     fn drop(&mut self) {
  20         println!("Dropping {}", self.0);
  21         let old = LOG.load(Ordering::SeqCst);
  22         let _ = LOG.compare_exchange(
  23             old,
  24             old << 4 | self.0 as usize,
  25             Ordering::SeqCst,
  26             Ordering::SeqCst,
  27         );
  28     }
  29 }
  30
  31 fn main() {
  32     fn die() -> D { panic!("Oh no"); }
  33     let g = thread::spawn(|| {
  34         let _nested = vec![vec![D( 1), D( 2), D( 3), D( 4)],
  35                            vec![D( 5), D( 6), D( 7), D( 8)],
  36                            vec![D( 9), D(10), die(), D(12)],
  37                            vec![D(13), D(14), D(15), D(16)]];
  38     });
  39     assert!(g.join().is_err());
  40
  41     // When the panic occurs, we will be in the midst of constructing the
  42     // second inner vector.  Therefore, we drop the elements of the
  43     // partially filled vector first, before we get around to dropping
  44     // the elements of the filled vector.
  45
  46     // Issue 23222: The order in which the elements actually get
  47     // dropped is a little funky: as noted above, we'll drop the 9+10
  48     // first, but due to #23222, they get dropped in reverse
  49     // order. Likewise, again due to #23222, we will drop the second
  50     // filled vec before the first filled vec.
  51     //
  52     // If Issue 23222 is "fixed", then presumably the corrected
  53     // expected order of events will be 0x__9_A__1_2_3_4__5_6_7_8;
  54     // that is, we would still drop 9+10 first, since they belong to
  55     // the more deeply nested expression when the panic occurs.
  56
  57     let expect = 0x__A_9__5_6_7_8__1_2_3_4;
  58     let actual = LOG.load(Ordering::SeqCst);
  59     assert!(actual == expect, "expect: 0x{:x} actual: 0x{:x}", expect, actual);
  60 }