On 10/26/2010 04:46 PM, Andrei Alexandrescu wrote:
In this particular case the decision goes both ways, and both have
something going for them. You may want to submit a bug report at least
to prompt us to change the documentation to clarify the behavior.
A workaround is to define opAssign(Bar).

I do not see how defining opAssign would help here. I want to nullify local reference to a Bar instance (to let GC dispose of Bar object, for example). I do not need to change Bar or Foo.

Anyway, I filed bug report: http://d.puremagic.com/issues/show_bug.cgi?id=5123

Reply via email to