Object.mixin was doing that through Object.getOwnPropertyNames ... that is what I would expect any `$.extend` would do too but I feel naive here ^_^
Niceness On Sat, Jan 11, 2014 at 1:28 PM, Axel Rauschmayer <[email protected]> wrote: > * At the moment, only Object.keys and the for-in loop are affected by it. > * In ECMAScript 6, Object.assign will also ignore non-enumerable > properties. > > > Pave that cowpath! > > > I’m sorry for being difficult, but IMO this is an important point: The > current cowpath is for-in style, right? That is, inherited and own > non-enumerable properties. We’ll deviate from that anyway. Independently of > what enumerability means, I can only think of cases (including Claude > Pache’s pro-enumerability example) where I would want to copy *all* own > properties. > > Axel > > -- > Dr. Axel Rauschmayer > [email protected] > > home: rauschma.de > twitter: twitter.com/rauschma > blog: 2ality.com > > > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
