On heap segregation, GC optimization and @nogc relaxing

[deadalnix via Digitalmars-d]

On Tuesday, 18 November 2014 at 02:39:48 UTC, Walter Bright wrote:
> On 11/17/2014 1:57 PM, deadalnix wrote:
>> 2. I'm not sure if that is enough to make it work. It is worth
>> investigating. It is gonna be much more limited than what I 
>> have
>> in mind.
>
> There was a lot of skepticism initially when I proposed that 
> ref be a storage class rather than a type constructor, but it 
> turned out that the problems were resolvable and the end design 
> was an unqualified win. So I think we can do this - at a 
> minimum we need to exhaust the possibility.

ref only make sense at interface boundary. That is not the same
thing.