Mark S. Miller (2013-07-17T01:51:26.000Z)
On Tue, Jul 16, 2013 at 6:33 PM, Luke Hoban <lukeh at microsoft.com> wrote:

>  All current engines I could try return Number.prototype for:****
>
> ** **
>
> 12[“__proto__”]****
>
> ** **
>
> But the new spec says this should be a TypeError.
>

What is the relevant part of the new spec?



> ****
>
> ** **
>
> It’s more consistent with the other members of Object.prototype to do an
> implicit ToObject here, and apparently matches existing implementations.
> Is it intentional that the spec is treating this as a TypeError?****
>
> ** **
>
> Luke****
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>


-- 
    Cheers,
    --MarkM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130716/47fafabb/attachment.html>
domenic at domenicdenicola.com (2013-07-23T02:37:01.270Z)
On Tue, Jul 16, 2013 at 6:33 PM, Luke Hoban <lukeh at microsoft.com> wrote:

>  All current engines I could try return `Number.prototype` for:
>
> ```js
> 12["__proto__"]
> ```
>
> But the new spec says this should be a `TypeError`.

What is the relevant part of the new spec?