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

Kagamin via Digitalmars-d digitalmars-d at puremagic.com
Fri Mar 3 08:38:52 PST 2017


On Friday, 3 March 2017 at 02:11:38 UTC, Moritz Maxeiner wrote:
> My major gripe, though, is still that people tend to create 
> "safe" wrappers around "unsafe" (mostly) C libraries, which (in 
> the sense of safety) doesn't really help me as a developer at 
> all

Wrappers are needed because C libraries have unsafe (and 
underdocumented) API that's easy to get wrong. I saw it happening 
twice in druntime. Safety is like optimization: you can handle it 
one or twice, but code handles it always, that makes a difference.


More information about the Digitalmars-d mailing list