Scoped thread panic messages unexpectedly interleaving in stderr output

[AronParker]

Consider the following code:

use crossbeam_utils::thread;

fn main() {
    thread::scope(|s| {
        s.spawn(|_| {
            panic!("AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA");
        });

        s.spawn(|_| {
            panic!("BBBBBBBBBBBBBBBBBBBBBBBBBBBBB");
        });
    });
}

When running it will interleave the panic messages written to stderr:

thread 'thread '<unnamed><unnamed>' panicked at '' panicked at 'BBBBBBBBBBBBBBBBBBBBBBBBBBBBBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA', src\main.rs:12:13

or

thread 'thread '<unnamed>' panicked at 'BBBBBBBBBBBBBBBBBBBBBBBBBBBBB', <unnamed>' panicked at 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA', src\main.rs:src\main.rs10::6:13

or

thread '<unnamed>' panicked at 'thread '<unnamed>' panicked at 'BBBBBBBBBBBBBBBBBBBBBBBBBBBBB', src\main.rs:AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA', src\main.rs10::13

This hurts readability. I believe in order to fix this, it would be helpful to preferably suppress the output. Alternatively one could serialize the writes, but given that spawn() provides a Result with the panic, I believe it is best left to the programmer on what to do with the panic.

[AronParker]

Apparently this is a rust issue: rust-lang/rust#96706 (comment)

[taiki-e]

This is not a problem specific to scoped threads, so any "fixes" (if exist) on this need to be done upstream.