> 1. Is it feasible?
If detecting that an object had been *dereferenced* was a straightforward
problem, then we could do something much better than a callback. The problem
is that detection of unreferenced objects is a hard problem. On the other
hand if what you mean by "dereference" is just "removal from a collection"
well, that would probably be trivial to implement. However, it seems of
fairly minimal value, since the application already knows it just removed an
object from a collection.
> 2. Is this a good idea performance wise, and design wise.
performance is not really the issue.
defining exactly what are the semantics of "dereferenced" would be the real
problem.
|