Should __proto__ be an accessor property of Object.prototype?

2013-06-22 Thread Rick Waldron
On Saturday, June 22, 2013, Nathan Wall wrote: See this thread: https://mail.mozilla.org/pipermail/es-discuss/2013-May/030551.html Further resolution here: https://github.com/rwldrn/tc39-notes/blob/master/es6/2013-05/may-21.md I'm on my mobile and the fragment URL doesn't seem to work? Look

Re: Should __proto__ be an accessor property of Object.prototype?

2013-06-22 Thread Erik Arvidsson
On Sat, Jun 22, 2013 at 1:15 PM, Rick Waldron waldron.r...@gmail.com wrote: Pesudocode: Object.defineProperty(Object.prototype, '__proto__', { get: function(){ return Object.getPrototype(this) }, set: function(v){ return Object.setProrotype(this, v) }, enumerable: false,

Should __proto__ be an accessor property of Object.prototype?

2013-06-21 Thread BelleveInvis
The current behaviour of __proto__ looks ugly. The better way might be make __proto__ an unconfigurable accessor of Object.prototype Pesudocode: Object.defineProperty(Object.prototype, '__proto__', { get: function(){ return Object.getPrototype(this) }, set: function(v){ return

Re: Should __proto__ be an accessor property of Object.prototype?

2013-06-21 Thread Nathan Wall
See this thread: https://mail.mozilla.org/pipermail/es-discuss/2013-May/030551.html On Fri, Jun 21, 2013 at 11:34 PM, BelleveInvis infinte.c...@hotmail.comwrote: The current behaviour of __proto__ looks ugly. The better way might be make __proto__ an unconfigurable accessor of