More radical ideas about gc and reference counting

[Jacob Carlborg via Digitalmars-d]

On 2014-05-02 17:38, "Marc Schütz" <schuetzm at gmx.net>" wrote:

> But my main point was actually this:
> Don't disallow destructors on classes just because they are classes, but
> disallow them when they are not guaranteed to be called (or calling them
> is troublesome because of multi-threading), i.e. GC.

Tango for D1 added a "dispose" method to Object. This method was called 
when "delete" or "scope" was used.

-- 
/Jacob Carlborg