RFC: Change what killing a thread does on error instead

Derek Fawcus dfawcus+dlang at employees.org
Tue Jul 8 20:40:46 UTC 2025


On Tuesday, 8 July 2025 at 20:24:06 UTC, Sebastiaan Koppe wrote:
> On Tuesday, 8 July 2025 at 19:55:13 UTC, Dukc wrote:
> That is similar to what happens with structured concurrency. 
> For every execution context there is always an owner to which 
> any Error gets forwarded to, all the way up to the main thread.
>
> It would be straightforward to change that so that it 
> terminates the process on the spot, but I prefer graceful 
> shutdown instead.

It was mentioned up thread that this could be an exception. Was 
that supposed to be the language exception, or also include CPU 
exceptions - resulting in signals under unix?

For the latter, I want the process to crash and core dump by 
default, not have something try and catch SIGSEGV, SIGBUS, SIGFPE 
etc.


More information about the Digitalmars-d mailing list