> On Feb 12, 2015, at 8:35 AM, Andrea Giammarchi <andrea.giammar...@gmail.com>
> wrote:
>
> Without going down full specification/implementation details, does anyone
> believe that classes should/could be used, in the future, as traits/mixins
> too?
>
> I find that an anty pattern.
>
> I think traits should be just plain objects with an initializer or some
> special object flagged as trait and I'd rather leave inheritance and classes
> features outside this future feature.
>
> Thoughts? Thanks!
I would agree with that. I had a trait implementation that used classes as
traits, and it caused a lot of problems, especially since classes have
constructors. Traits should not have constructors. I have since updated my
implementation to use plain objects.
This is what I am using now:
https://gist.github.com/lukescott/36453a75c39c539f5c7d
<https://gist.github.com/lukescott/36453a75c39c539f5c7d>
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
