-
-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New halt implementation #18026
New halt implementation #18026
Conversation
…he compiler, parse, semantic analysis and the rest
As a bonus no need for the compiler, not reparse and semantical analysis. |
Working on reimplementing HaltCount: too. |
@@ -184,24 +193,36 @@ Halt class >> onCountWithBehavior: behaviorBlock [ | |||
Halt class >> once [ | |||
"Stop once and only once the execution of the method containing the expression Halt once. If you need to get it stops another time after the first stop, use Halt resetOnce." | |||
|
|||
| callingContext senderContext node | | |||
<debuggerCompleteToSender> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe the pragma should be kept, because this is used to hint the debugger that this method should be filtered from the shown stack by default (and usually we want to stop at the caller, not here right?
Or maybe it's not needed? What does the debugger show when this halts without the pragma?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean, if you do Halt once
directly in a method
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tx I thought that I kept it so I will added back
Now there is a bug because we should not be forced to do Halt initializeOnCount before. I just commit to get a stable point.
…his is mandatory else running twice the test will fail."
Ready for review. |
a new implementation of haltOnce with nice tests showing that
executing two times in a row the same haltOnce call will bark only the first time and
that we can have multiple call sites in the same method with each one their own "counter"