If that's true then a switch seems over complicated so it's easier to keep
enumerability as it is now: nobody will have surprises in this way.
Best Regards
On Mon, Jan 13, 2014 at 6:46 AM, Boris Zbarsky <bzbarsky at mit.edu> wrote:
> On 1/12/14 11:57 PM, Andrea Giammarchi wrote:
>
>> Recap: it seems we agree classes properties and methods should not show
>> up in a for/in
>>
>
> I should note that web developers commonly expect DOM methods/properties
> to show up in for/in (and in fact often write code depending on that,
> sometimes depending on the order of the enumeration). So to the extent
> that we're trying to align DOM stuff with ES6 classes, we may need a
> class-level switch to decide whether a particular class has enumerable
> members or something. :(
>
> -Boris
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140113/fd69aacc/attachment.html>
domenic at domenicdenicola.com (2014-01-17T23:54:59.459Z)
If that's true then a switch seems over complicated so it's easier to keep
enumerability as it is now: nobody will have surprises in this way.
