meanwhile, if V8 devs would like to play with the "how knows if/where to
put it" proposal, I've landed a patch that polish __proto__ poison from V8
and add, with tests I could think of, Object.setPrototypeOf native:
https://code.google.com/p/v8/issues/attachmentText?id=2675&aid=26750000000&name=set-prototype-of.patch&token=EgU0cdPaKMv9s2o9u0j57Mgu53A%3A1368055395105
premature, I know, but I could not resist :D
On Wed, May 8, 2013 at 4:10 PM, Brendan Eich <bren...@mozilla.com> wrote:
> Jeff Walden wrote:
>
>> On 05/08/2013 01:58 PM, Brendan Eich wrote:
>>
>>> 1. Dumping stuff into Annex B to show disdain. This is pride, bad for
>>> the soul.
>>>
>>
>> "Pride" doesn't seem like a reason one way or the other, to me.
>>
>
> Good.
>
>
> The reason would be to cordon off functionality whose mis-performance
>>
>
> Why would Object.setPrototypeOf have any better perf?
>
>
> developers will not intuitively understand, so that they're less likely
>> to use it. Some will, even still, perhaps just out of obstinacy ("pride",
>>
>
> I think you missed that that was directed at TC39ers, not developers.
>
>
> even, that they hacked their way to the tiniest solution :-) ). But
>> some will take a second look, learn the reasons it's undesirable, and not
>> use it.
>>
>
> And not use Object.setPrototypeOf?
>
> /be
>
> ______________________________**_________________
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/**listinfo/es-discuss<https://mail.mozilla.org/listinfo/es-discuss>
>
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
