generated from tc39/template-for-proposals
-
Notifications
You must be signed in to change notification settings - Fork 54
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
cross realm signals #219
Comments
My first thought is, to stay conservative, we should make tracked reads throw when the current computed is from a different Realm. This will ensure that Realms do not have entangled dependency graphs (which, in the case of ShadowRealms, would give us something a bit unworkable when it comes to introspection). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the expected interactions of signals across realms, whether the callable boundary of ShadowRealms is involved or not.
In particular:
subtle.currentComputed()
return while executing a function in a realm different from where the "current computed" originated.get
function "bound" to its signal). How would these dependencies be exposed without violating the callable boundary invariants.The text was updated successfully, but these errors were encountered: