>>31
Yeah, that's horrible. I don't think you're ``supposed'' to write programs with exceptions in Go, though, so they have only themselves to blame. With the kind of hyper-robustness they are probably aiming for, it seems better to handle truly exceptional circumstances at the thread or process level by bailing out and letting the monitor thread restart you.