Missing stacktrace on memory allocation failure

[mw]

On Thursday, 12 November 2020 at 13:16:21 UTC, Steven 
Schveighoffer wrote:
> On 11/12/20 4:22 AM, Per Nordlöw wrote:
>> Why don't I get a stack trace on Memory allocation exceptions?
>> 
>> In my case I only get:
>> 
>> src/core/exception.d(647): [unittest] Memory allocation failed
>> core.exception.OutOfMemoryError at src/core/exception.d(647): 
>> Memory allocation failed
>> 
>
> Certain errors are flagged as not able to allocate memory. So 
> you don't get a stack trace.
>
> I think it's a huge mistake, and we don't need memory 
> allocation to do stack trace printing. But that's the way it is.

Hit this one today, since it's a mistake, what does it take to 
fix it? or you are saying it's unfix-able in the current D 
runtime?