Re: Proposal revisions: "Draft Proposed Standard SES" becomes "Draft Proposed Frozen Realm API"

On Tue, Mar 29, 2016 at 7:02 AM, Mark S. Miller wrote: > [...]The main reason for listing something in Annex B: > > * It is normative optional -- if the feature exists at all, it must > exist like so. > As the proposal says: Some of the elements of Annex B are safe and

Re: Proposal revisions: "Draft Proposed Standard SES" becomes "Draft Proposed Frozen Realm API"

Moving discussion to https://github.com/FUDCo/frozen-realms/issues/14 , not a fan. On Tue, Mar 29, 2016 at 9:04 AM, Mark S. Miller wrote: > > > On Tue, Mar 29, 2016 at 6:50 AM, Mark S. Miller > wrote: > >> Good question! >> >> Regarding the existing

Re: Proposal revisions: "Draft Proposed Standard SES" becomes "Draft Proposed Frozen Realm API"

On Tue, Mar 29, 2016 at 6:50 AM, Mark S. Miller 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

Re: Proposal revisions: "Draft Proposed Standard SES" becomes "Draft Proposed Frozen Realm API"

On Tue, Mar 29, 2016 at 6:54 AM, Bradley Meck wrote: > 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

Re: Proposal revisions: "Draft Proposed Standard SES" becomes "Draft Proposed Frozen Realm API"

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,

Re: Proposal revisions: "Draft Proposed Standard SES" becomes "Draft Proposed Frozen Realm API"

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

Re: Proposal revisions: "Draft Proposed Standard SES" becomes "Draft Proposed Frozen Realm API"

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.

Proposal revisions: "Draft Proposed Standard SES" becomes "Draft Proposed Frozen Realm API"

At https://github.com/FUDCo/ses-realm Since I last posted this, I have received much useful feedback of this proposal, especially from Daniel Ehrenberg, Ojan Vafai, Elliott Sprehn, Alex Russell, and Dave Herman. Thanks! This revision addresses this feedback in a variety of ways: * By