nothrow by default

[Jonathan M Davis]

On Thursday, January 9, 2020 8:25:17 PM MST Timon Gehr via Digitalmars-d 
wrote:
> On 10.01.20 02:28, Walter Bright wrote:
> > On 1/9/2020 2:10 PM, Timon Gehr wrote:
> >> On 09.01.20 11:32, Jonathan M Davis wrote:
> >>> I wouldn't mind us getting rid of Error in favor of killing the
> >>> program on
> >>> the spot, since that's actually better for debugging,
> >>
> >> It really depends. There are situations where it may be better, but if
> >> you are trying to debug a non-deterministic condition that happens
> >> very rarely on someone else's machine exclusively in release builds,
> >> depending on a lot of user input, druntime shutting down the code that
> >> is supposed to collect enough information for you to have a chance to
> >> figure out what is going on in detail can hardly be described as
> >> "better". It should be possible to hook the kill function at least.
> >
> > Hooking the kill function is the way to do that - much better than
> > exception unwinding.
>
> Exception unwinding gives you a stack trace.

A core dump at the point of the error gives you that and more.

- Jonathan M Davis