Vision for the D language - stabilizing complexity?

Kagamin via Digitalmars-d digitalmars-d at puremagic.com
Fri Aug 5 09:24:32 PDT 2016


On Monday, 11 July 2016 at 18:57:51 UTC, deadalnix wrote:
> Alright, but keep in mind that is an example, not the actual 
> problem I'm talking about. There are many reasonable way to 
> make the example above safe: disallow dereferencing pointers 
> from unknown source, do a bound check on .ptr, disallow .ptr 
> altogether and much more.
>
> The root problem is that "@safe guarantee memory safety and if 
> it doesn't it is a bug" provides no information as to what is 
> the bug here and no actionable items as to how to fix it, or 
> even as to what needs fixing.

Saw it on reddit: how rust manages safety bugs: 
https://www.reddit.com/r/programming/comments/4vto4r/inside_the_fastest_font_renderer_in_the_world/d61ltp8


More information about the Digitalmars-d mailing list