On Feb 12, 2012, at 11:28 AM, Brendan Eich wrote: > Heh, I knew that was coming. I'll amend to say "of long standing" after > "implementations" :-P.
:-D > I still have a gut feeling that someone is going to take advantage of the > setter for bad purposes that will be harder to block than would be the case > if __proto__ reflected as a data property. But I can't prove this. Understood. We needed to change our implementation to fix ES5 compatibility issues with our prior mechanism. Implementing this internally as a accessor is much cleaner for us, and I think we'd want to keep it implemented this way even if we were to add the magic necessary to allow us to make it masquerade as a data descriptor (I still firmly side with Mark's strawman as to how this should be presented to users, but I didn't intend our current implementation to preclude alternatives). cheers, G.
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
