-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix(swingset): gc-actions: new algorithm, update test #3296
Conversation
64de132
to
a3a3f67
Compare
Implement the new algorithm to decide when a GC Action should be negated or bypassed.
a3a3f67
to
6c85e21
Compare
const owner = kernelKeeper.ownerOfKernelObject(kref); | ||
if (owner) { | ||
return kernelKeeper.getObjectRefCount(kref); | ||
function filterAction(vatKeeper, action, type, kref) { |
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.
This probably could use a comment explaining why the actions are being filtered, since the verb "filter" is pretty generic, i.e., what the respective meanings of the pre-filtration and post-filtration collections are supposed to be. I think what's happening is it's throwing away the actions that it's not actually going to perform this time through, but I'm not 100% sure my understanding is correct.
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.
This makes sense now.
Implement the new algorithm to decide when a GC Action should be negated or
bypassed. This is intended to match the new contents of docs/garbage-collection.md .
refs #3106