Is __proto__ ready needed?
andrea.giammarchi at gmail.com
Mon Jun 10 11:14:45 PDT 2013
yep, that's awesome ... too bad not a single engine exposed yet such easy
change ever for both V8 and/or SpiderMonkey since everything is already in
place, only the public method exposed to JS is missing (and for V8 I've
already porposed a patch to drop the poison pill but nothing happened ...)
I just hope V8 will do this change before node.js will be out in its
"final" 1.0 version and looking forward to see FF nightly and mobile
adopting that too.
On Mon, Jun 10, 2013 at 8:31 AM, Rick Waldron <waldron.rick at gmail.com>wrote:
> On Mon, Jun 10, 2013 at 10:50 AM, medikoo <medikoo+mozilla.org at medikoo.com
> > wrote:
>> Object.setPrototypeOf is really needed.
> From the meeting notes:
> Conclusion: __proto__ is an accessor on Object.prototype. The setter
> mutates [[Prototype]]. There is no “poison pill”. We will provide both
> Object.setPrototypeOf and std:reflect setPrototypeOf.
>> Use cases for that are as rare as for eval, but exist and are valid.
>> heavily on __proto__.
>> Once I was asked By David Herman to explain my use cases. I prepared
>> following gist then: https://gist.github.com/medikoo/5602644
>> View this message in context:
>> Sent from the Mozilla - ECMAScript 4 discussion mailing list archive at
>> es-discuss mailing list
>> es-discuss at mozilla.org
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss