This requirement is not specified in EcmaScript, and I have started playing around with `null` inheriting globals. I do not want it explicitly mandated by this if ES does not mandate it. Is there a reason it is a mandate and not an Annex that is there due to some parts of the ecosystem?
On Tue, Mar 29, 2016 at 8:50 AM, Mark S. Miller <[email protected]> wrote: > Good question! > > Regarding the existing global, the frozen realm API proposal does not say > anything at all -- it is concerned only about TheFrozenRealm and realms > descendant from it. Outside of the frozen realm proposal, I would indeed > like us to pin this down better for globals in general. Why only in the > Annex? If we can get agreement to pin it down, I would prefer that it be in > the main normative-mandatory text. > > Regarding the global of TheFrozenRealm, I did not intend to underspecify > that. This is an oversight that I will fix. When I said "the global of > TheFrozenRealm is a plain object" I had in mind that it would inherit > directly from Object.prototype. I will revise to say that explicitly. > Thanks! > > > > > On Tue, Mar 29, 2016 at 6:34 AM, Bradley Meck <[email protected]> > wrote: > >> Does this mandate that the global inherit from any specific prototype? >> Most cases in the wild inherit from Object at some point, but I feel that >> should only be in the Annex. Several large libraries depend on this, but it >> is not strictly required for all libraries. >> > > > > -- > Cheers, > --MarkM >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
