Safety, undefined behavior, @safe, @trusted

[Andrei Alexandrescu]

Steven Schveighoffer wrote:
> On Thu, 05 Nov 2009 16:30:42 -0500, Andrei Alexandrescu 
> <SeeWebsiteForEmail at erdani.org> wrote:
> 
>>>  Most of the usages are like this:
>>>  ubyte[1024] buffer;
>>> functionThatNeedsBufferSpace(buffer);
>>>  where functionThatNeedsBufferSpace takes a ubyte[], thereby taking 
>>> an address of the local data.
>>>  So it's not explicit address taking, but it's the same thing under 
>>> the hood.  There always exists the potential for the stack reference 
>>> to escape.
>>
>> I see, thank you. I am confident that a trusted reap could be 
>> implemented in the standard library. (google reap)
> 
> I did.  Couldn't find anything.

Damn acronyms, sorry. Better results: reap memory allocation

ftp://ftp.cs.utexas.edu/pub/emery/papers/reconsidering-custom.pdf


Andrei