Replace WatchExprBreakpoint with WatchIVarBreakpoint #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the discussion in #49, having
WatchExprBreakpoint
for watch all expression changes costs too much on performance but provide limited benefit to the users. But because watching instance variables for state changes is still valuable for debugging, we're going to support this particular case.So in this PR, I made these changes:
WatchExprBreakpoint
withWatchIVarBreakpoint
.watch expr
is no longer supported.watch @ivar
is more accurate and cheaper.About WatchIVarBreakpoint
Currently, when watching instance variables, the breakpoint isn't aware of the instance/class it's tracking on. So it could incorrectly track instance variable change (with the same name) in a different class.
For example, if you debug this script:
You'll find that it stops at
Teacher
's@name
assignments as well, even though the script should only monitorStudent
's@name
.After
Another benefit of the change is that we can show what instance's ivar is changed:
(I plan to work on styling it in another PR)