what I think is a very valid use case for mixins based on ES5 features var MixIt = Object.defineProperties({}, { name: { enumerable: true, get: function () { // notify or do stuff return this._name; }, set: function (_name) { // notify or do stuff this._name = _name; } }, _name: { writable: true } });
while super is unknown concept in ES5 but if de-sugared as Constructor.prototype.method.call(this, argN) in ES6 then is implicitly valid/doesn't need to be modified? br On Tue, Dec 11, 2012 at 10:29 AM, Rick Waldron <waldron.r...@gmail.com>wrote: > > > > On Tue, Dec 11, 2012 at 1:27 PM, Allen Wirfs-Brock > <al...@wirfs-brock.com>wrote: > >> >> 2) It needs to rebind super references >> >> 3) I don't see any reason that it should be restricted to enumerable >> >> properties. If the intend is to deprecate enumerable along with for-in >> then >> >> we should be adding new functionality that is sensitive to the state >> of the >> >> enumerable attribute. >> > >> > "should not"? >> >> Right, should not! >> > > To clarify, I assumed you meant "should not", based on the rationale and > that is what I was agreeing to. > > Rick > > > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss