Once upon a time we actually had Traits in the pre-maxmin-classes implementation in Traceur. We've removed it as the class proposal is now radically different, but I'm hopeful that once classes are "baked", traits will be one of the important improvements we can add quickly.
Getting there requires that we have a solid proposal, so perhaps the first thing to do here is to look back at the trait syntax we had before, decide what you did and didn't like, and work with us to come up with a new straw-man for ES7. Once we've got something we like, we can prototype in Traceur. Sound good? On Fri, Sep 21, 2012 at 4:16 PM, Tom Van Cutsem <[email protected]> wrote: > Hi, > > 2012/9/21 Aron Homberg <[email protected]> >> >> Does the strawman/traits_semantics document reflect the recent common >> understanding how traits should be implemented? >> > > No: traits are not currently being considered for ES6. Instead, the > committee chose to go for a more minimal approach that provides better > support for current best practices and patterns based on prototypal > (single-)inheritance. > > As a meta-point, notice that the traits/semantics wiki page lives under > the "strawman:" namespace. These are proposals that have not (yet) gained > consensus. Proposals that have reached consensus in the committee live > under the "harmony:" namespace, cf. < > http://wiki.ecmascript.org/doku.php?id=harmony:proposals>. > > Cheers, > Tom > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
