Andrea Giammarchi andrea.giammarchi at gmail.com
Sun Jan 12 21:14:17 PST 2014

classes do not exist today and your example was about direct object, not
inherited from classes as they are meant in ES6.

I see from both here and Twitter you took this in a very wrong way while I
was asking rationale from those Allen's quotes you actually rephrased so I
just stop here.

All good, for/in with classes properties/methods is all we wanted/needed in
ES6, thanks.

Best Regards

On Sun, Jan 12, 2014 at 9:05 PM, Rick Waldron <waldron.rick at gmail.com>wrote:

> On Sun, Jan 12, 2014 at 11:57 PM, Andrea Giammarchi <
> andrea.giammarchi at gmail.com> wrote:
>> Recap: it seems we agree classes properties and methods should not show
>> up in a for/in ...
> No we don't agree, because that's inconsistent with the behaviour that
> exists today.
> Rick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140112/df40fef6/attachment.html>

More information about the es-discuss mailing list