RFC: Change what assert does on error

[Adam Wilson]

On Friday, 4 July 2025 at 06:29:26 UTC, Walter Bright wrote:
> On 7/3/2025 12:21 AM, Adam Wilson wrote:
>> It is an absolute non-negotiable business requirement that I 
>> be able to get debugging information out of the server without 
>> physical access to the device. If you won't deliver the 
>> logging data, corrupted or not, on an assert, then no business 
>> can justify using D in production.
>
> I did mention that logging the error before terminating the 
> process was acceptable. My point is that recovering is not 
> acceptable.

Kinda hard to do that when the process terminates, especially if 
the logger is a side-thread of the app like it was on my team at 
MSFT.

But also, not printing a stack trace means there is nothing to 
log.