Skip to content
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

feat(vat-data): virtual exos are internally revocable #8014

Closed
wants to merge 1 commit into from

Conversation

erights
Copy link
Member

@erights erights commented Jul 6, 2023

Alternative to #8020 with internal revocability

Extracted from Spike at #8009 because it is already mergeable without #8009's other support

Mirrors endojs/endo#1668 but does not depend on it.

@erights erights requested a review from FUDCo July 6, 2023 04:08
@erights erights self-assigned this Jul 6, 2023
@erights erights changed the title feat(vat-data): virtual exos are -nternally revocable feat(vat-data): virtual exos are internally revocable Jul 6, 2023
Base automatically changed from markm-cleanups-from-8009 to master July 6, 2023 07:36
@erights erights force-pushed the markm-internal-revocables branch from cdf3450 to b38139b Compare July 6, 2023 07:38
@@ -920,15 +920,25 @@ export const makeVirtualObjectManager = (
const makeContext = (baseRef, state) => {
// baseRef came from valToSlot, so must be in slotToVal
const val = requiredValForSlot(baseRef);
const revoke = () => contextCache.delete(baseRef);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@FUDCo do I need to register this object for some internal gc purpose? Does it being a function raise any additional issues?

@erights erights marked this pull request as draft July 6, 2023 15:37
@erights
Copy link
Member Author

erights commented Jul 7, 2023

Reversed decision. Now closing in favor of #8020

@erights erights closed this Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant