If you needed any more evidence that memory safety is the future...

[Moritz Maxeiner via Digitalmars-d]

On Wednesday, 8 March 2017 at 13:30:42 UTC, XavierAP wrote:
> On Wednesday, 8 March 2017 at 12:42:37 UTC, Moritz Maxeiner 
> wrote:
>> Doing anything else is reckless endangerment since it gives 
>> you the feeling of being safe without actually being safe. 
>> Like using @safe in D, or Rust, and being unaware of unsafe 
>> code hidden from you behind "safe" facades.
>
> Safe code should be unable to call unsafe code -- including 
> interop with any non-D or binary code, here I agree. I was 
> supposing this is already the case in D but I'm not really sure.

You can hide unsafe code in D by annotating a function with 
@trusted the same way you can hide unsafe code in Rust with 
unsafe blocks.