I'm a JS programmer with more decades of experience than I care to mention, and follow developments in language design closely. Frankly, I don't understand what you are trying to accomplish or why support for it needs to be in the language. I strongly doubt I'm the only one. Rather than spending your time tilting at TC39 windmills, I'd suggest a focus on putting together a library which implements your vision of mixins.
Bob On Sat, Nov 18, 2017 at 11:12 PM, Raul-Sebastian Mihăilă < [email protected]> wrote: > On Sat, Nov 18, 2017 at 7:19 PM, Isiah Meadows <[email protected]> > wrote: > >> Protocols are not mixins - they're interfaces. They specify minimum >> behavior required to implement (their primary focus), not simply extended >> behavior. In particular, protocols and mixins would be more complementary >> than conflicting. >> > Protocols are mixins as well, take a look at this comment. > https://github.com/michaelficarra/proposal-first- > class-protocols/issues/29#issuecomment-344343842 > Also, I didn't say they conflict with mixins, I said they should be > separate. > > _______________________________________________ > 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
