classes and enumerability
russell.leggett at gmail.com
Tue Dec 23 21:09:42 PST 2014
On Wednesday, December 24, 2014, Kevin Smith <zenparsing at gmail.com> wrote:
> The question is: what should ES6 classes choose as the default? What's the
>> most useful default, independent of various backward-looking consistencies?
>> What, if the future is bigger than the past, would be best?
> Framed that way, then non-enumerability.
> If we want to preserve any kind of conceptual integrity for enumerability,
> then enumerability must indicate that the property is a data element within
> a data structure.
> Whether enumerability is worth preserving, I don't know.
> I'll just throw out mixins as a possible reason to keep enumerability.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss