A lot of core.thread functions are not nothrow because they escalate errors of the underlying implementation (pthread, Windows threads) by throwing a ThreadException. Most of those functions should only fail on resource exhaustion and recovering from that is a bit tricky. So I wonder if we should handle them as fatal errors and mark the high-level core.thread functions as nothrow.
Comment #1 by robert.schadek — 2024-12-07T13:34:31Z