andrea.giammarchi at gmail.com
Sat Jan 11 14:05:32 PST 2014
Object.mixin was doing that through Object.getOwnPropertyNames ... that is
what I would expect any `$.extend` would do too but I feel naive here ^_^
On Sat, Jan 11, 2014 at 1:28 PM, Axel Rauschmayer <axel at rauschma.de> 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
> 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
> Dr. Axel Rauschmayer
> axel at rauschma.de
> home: rauschma.de
> twitter: twitter.com/rauschma
> blog: 2ality.com
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss