On 30 Sep 2015, at 17:45, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
I think this should be Ok for most inspector cases because we rarely open the object in the middle of a method and expect it to be updated within that same method. Or did I get it wrong?
if you want to do change tracking by interception all writes, than any update in a loop (that accesses the ivar directly) that is active already before the inspector is opened would be not seen. I do not think this happens often. Possible solutions: - detect this case âthere is method on the stack accessing this ivar â> do slow update, or display a warning that automatic update might not work) - Implement on-stack replacement for e.g. just #before links⦠- use another mechanism to detect state change Marcus