A safer interface for core.stdc

Tobias Pankrath via Digitalmars-d digitalmars-d at puremagic.com
Sun Feb 8 02:31:14 PST 2015


> come to think of it, is there any point in making malloc 
> @safe/@trusted
> at all? I don't think it's possible to make free() @safe, so 
> what's the
> purpose of making malloc callable from @safe code?

At least two programs, widely used by folks here, never release 
their memory. Those could be made @safe.


More information about the Digitalmars-d mailing list