-
Notifications
You must be signed in to change notification settings - Fork 4
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 abort / kill API #5
Comments
Having |
Yes, descendent aborts should be handled by an Clearly, |
@bergie, this is the top of my wishlist :) |
I think we can close this one? |
wants:
n.killPath()
kill current path, same thing as else passing down error, stops at nearestcontinue
ortree
n.killTree()
, kills up to nearest tree, through anycontinue
n.killContestant()
kill execution up to nearest contest, same thing as making contestant loseBy far most useful would be
n.killPath
.Not sure about usefulness of killing up to nearest composite, but for that another method name maybe?
Another option would be
n.kill( type )
type in ['path', 'tree', 'composite', 'contest', 'root']
The text was updated successfully, but these errors were encountered: