B.3.1 The __proto__ pseudo property

Brendan Eich brendan at mozilla.com
Mon Apr 22 04:43:44 PDT 2013


Mark Miller wrote:
> On Sun, Apr 21, 2013 at 9:42 PM, Brendan Eich <brendan at mozilla.com 
> <mailto:brendan at mozilla.com>> wrote:
>
>     Ok, so (after pushing back based on recorded consensus, which I
>     think is fair), I'm ok with
>
>     * Object.prototype.__proto__ is configurable.
>
>     * o = {__proto__: p} semantics changes from ES5's [[Put]] to ES6's
>     [[SetInheritance]].
>
>     I'm not sure everyone agrees, but let's assume these two.
>
>     Why, given these, must Object.prototype.__proto__ not reflect at
>     all via Object.getOwnPropertyDescriptor?
>
>
> What? Where is that proposed? (And again, I am jumping into this 
> thread in the middle, so apologies for lack of context.)

Up-thread, near the o.p.:

https://mail.mozilla.org/pipermail/es-discuss/2013-April/029962.html

>     What about Object.getOwnPropertyNames? We have to sink some cost
>     somewhere, and TC39 had a January near-consensus of "accessor,
>     with get and set functions that throw on cross-realm |this| vs.
>     the accessor function". That seems the best solution to me still,
>     and it should fall out of cross-window/frame wrapper policy hooks
>     fairly cheaply in SpiderMonkey.
>
>
> That sounds good to me too. Where is the alternative explained?

https://mail.mozilla.org/pipermail/es-discuss/2013-April/029962.html 
which links to a PDF.

/be


More information about the es-discuss mailing list