Axel Rauschmayer (2014-01-11T21:28:11.000Z)
>> * 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
axel at rauschma.de

home: rauschma.de
twitter: twitter.com/rauschma
blog: 2ality.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140111/844a6464/attachment.html>
domenic at domenicdenicola.com (2014-01-17T23:52:11.367Z)
>> * 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.