Memory safe in D

[Alexandru Ermicioi]

On Tuesday, 19 March 2024 at 08:44:29 UTC, Alex wrote:
> On Monday, 18 March 2024 at 22:27:28 UTC, Walter Bright wrote:
>> It's a hardware exception, same as the null reference 
>> exception.
>
> Yes, but language runtime can catch it via operating system 
> mechanism and re-throw as language exception which can be 
> handled inside code.

I wonder how these exceptions will play, if they are thrown fron 
nogc code...

I'd assume that you can set only one handler for each hardware 
exception and that handler would need to know in what function 
this occured, nogc or gc one, so it can halt in nogc, and throw 
in gc methods.