typeof extensibility, building on my Value Objects slides from Thursday's TC39 meeting

Brendan Eich brendan at mozilla.com
Thu Aug 1 17:21:03 PDT 2013

I thought this was not all that interoperable. What exactly are the 
intersection semantics? Not object identity change!


Anne van Kesteren wrote:
> On Tue, Jul 30, 2013 at 7:15 PM, Brandon Benvie<bbenvie at mozilla.com>  wrote:
>> I fully admit that this may be overkill to support an edge case, and as I
>> said I don't even know if it's expected for multi-realm usage to happen.
> Nodes moving between documents (with their own globals) is certainly
> something that occurs frequently in the DOM. (We have not figured out
> whether the prototype object needs to change, whether it does not
> change and we run into garbage collection hell, or whether we mutate
> the identity of the object. I suspect if we defined operators for
> these kind of objects they would invoke adopt, depending on
> functionality.)
> XMLHttpRequest is also used across globals and its base URL is tied to
> the document base URL of the global it originated from (workers work
> different).
> Not sure how relevant either of these cases here, but platform objects
> definitely move between globals and given that you have synchronous
> access to everything the implications are generally not thought
> through and it's all expected to just work.

More information about the es-discuss mailing list