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.
Somewhat similar to #4 (q for Quit), but this one accepts a
max
that specifies a maximal number of calls before raising a KillError.I wrote this one this morning while debugging an infinite recursion (SystemStackTrace), which proved difficult to debug, because happening in rspec tests. A typical use could be:
The KillError naturally shows the stacktrace of the last 3 calls, which proved very nice for fixing my stuff this morning. In my case, since the
visit
method was not called on the same instance, I used the following trick:I don't know whether this has to be merged. It is basically a shortcut for something like: