1 warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
2 (see https://github.com/rust-lang/miri/issues/1388)
4 error: Undefined Behavior: Data race detected between Write on Thread(id = 3) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
5 --> $DIR/dangling_thread_async_race.rs:LL:CC
8 | ^^^^^^^^^ Data race detected between Write on Thread(id = 3) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
10 = help: this indicates a bug in the program: it performed an invalid operation, and caused Undefined Behavior
11 = help: see https://doc.rust-lang.org/nightly/reference/behavior-considered-undefined.html for further information
13 = note: inside closure at $DIR/dangling_thread_async_race.rs:LL:CC
15 note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
17 error: aborting due to previous error; 1 warning emitted