>> True, that’s the catch. Then it works for composing an inheritance hierarchy
>> (as in mixins as abstract subclasses).
>>
>> Another idea for `extends` (if there is more than one object that is being
>> extended):
>>
>> extends(comparable, enumerable, foo, bar) { ... }
>
> I'm not sure what the semantics of this would be. Are you inventing
> multiple-prototype inheritance? That's not going to happen.
Single inheritance, a prototype chain composed from the given objects, in the
given order. An infix operator is probably better for this, though.
--
Dr. Axel Rauschmayer
[email protected]
home: rauschma.de
twitter: twitter.com/rauschma
blog: 2ality.com
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
