-
Notifications
You must be signed in to change notification settings - Fork 6
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
[[Notifier]]'s realm depends on the caller of the GetNotifier abstract operation #8
Comments
Like I said in #3, we could use the realm of the callback function. This probably means that we need some intermediate objects since we don't know the realm of an object and we don't know the realm until we get to the callback. |
Which callback function? Objects only have one notifier. Are you suggesting we give them multiple notifiers, one per realm that's observing them? |
Yes. That is isomorphic to what I was trying to say. |
Aha! Multiple notifier objects seems like it might be a bigger change... |
We can have a single [[Notifier]] but create the user observable objects in the same realms as the callback functions. |
Closing this in favor for #3 |
[[Notifier]]
is initialized toundefined
when an object is created. This means that, for example:obj
's[[Notifier]]
is now in Realm 2, sinceGetNotifier
is called byEnqueueChangeRecord
.Ideally the
[[Notifier]]
should belong to the same realm as the object, but this might have implementation difficulties in some engines.The text was updated successfully, but these errors were encountered: