Then "nothing" happens. The default, correct, behaviour for "unhandled" errors is to abort the program. Rust apparently thinks it doesn't need this, because "poisoning". Which is a great thing, except it still doesn't excuse silently swallowing errors. It's one way to end up with a half-dead process. And considering Rust's overall strict handling of errors, it seems bizarrely counter-intuitive to go with the silent route here.
The .NET team went through the exact same process and ended up taking a breaking change in v2 to fix their handling of background exceptions (so now they crash the app unless you opt-in to handling them).
I described it here: https://github.com/rust-lang/rust/issues/19610
But it's closed pending writing an RFC and I haven't had time to figure that out yet.
Edit: I added the RFC: https://github.com/rust-lang/rfcs/pull/519
With the new, threads-only system, I think the only way out is abort.