draft proposal for ref counting in D

[Walter Bright]

Michel Fortin wrote:
Le 2013-06-30 à 16:32, Walter Bright  a écrit :

 > Amended as:
 >
 > 6. If a class or struct contains RC fields, calls to Release() for those 
fields will
 > be added to the destructor, and a destructor will be created if one doesn't 
exist already.
 > Release() implementations should take care to not destroy objects that are 
already destroyed,
 > which can happen if the objects are allocated on the GC heap and the GC 
removes a cycle of
 > refcounted objects.

Good advice. But... how do you implement that? For one thing, I doubt there's an 
API in the GC you can query for deleted objects, and if there was it'd be 
inefficient to call it for every call to Release. And also, will a virtual call 
to a function of a destroyed object work in the first place? It all seems quite 
fragile to me.