Luke Hoban (2013-07-17T01:33:19.000Z)
All current engines I could try return Number.prototype for:

12["__proto__"]

But the new spec says this should be a TypeError.

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130717/7928dfd1/attachment.html>
domenic at domenicdenicola.com (2013-07-23T02:38:02.295Z)
All current engines I could try return `Number.prototype` for:

```js
12["__proto__"]
```

But the new spec says this should be a `TypeError`.

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`?
domenic at domenicdenicola.com (2013-07-23T02:36:27.067Z)
All current engines I could try return `Number.prototype` for:

```js
12["__proto__"]
```

But the new spec says this should be a `TypeError`.

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`?