Safe reference counting cannot be implemented as a library

Joseph Rushton Wakeling via Digitalmars-d digitalmars-d at puremagic.com
Tue Oct 27 13:29:27 PDT 2015


On Tuesday, 27 October 2015 at 18:10:18 UTC, deadalnix wrote:
> The problem at hand here is escape analysis. The compiler must 
> be able to ensure that a reference doesn't escape the RC 
> mechanism in an uncontrolled manner. I'd like to add such 
> mechanism to the language rather than bake in reference 
> counting, as it can be used to solve other problem we are 
> facing today (@nogc exception for instance).

I would also have a definite interest in this for the direction 
I'm considering taking with an alternative std.random design.

Technically, I suspect my particular use-case is covered by 
DIP25, but a more comprehensive solution to escape analysis would 
definitely make it more secure.


More information about the Digitalmars-d mailing list