Could the compiler not allow fields on Mixins if it found them to be calculated?
brianWed 13 Mar 2013
Right now I require Mixin fields be abstract. I think maybe they could be calculated, although that might add quite a bit of complexity.
SlimerDudeFri 15 Mar 2013
As calculated properties contain no state, I see no reason why they can't defined in Mixins. And in doing so, it would allow a lot of Classes to be re-defined as Mixins - freeing up the precious inheritance hierarchy.
that might add quite a bit of complexity.
As the compiler already identifies calculated properties, I has hoping it wouldn't be that much work... :( Oh well.
brianWed 20 Mar 2013
Promoted to ticket #2110 and assigned to brian
Seems like a pretty reasonable thing to add, so lets track it
SlimerDude Wed 13 Mar 2013
Could the compiler not allow fields on Mixins if it found them to be calculated?
brian Wed 13 Mar 2013
Right now I require Mixin fields be abstract. I think maybe they could be calculated, although that might add quite a bit of complexity.
SlimerDude Fri 15 Mar 2013
As calculated properties contain no state, I see no reason why they can't defined in Mixins. And in doing so, it would allow a lot of Classes to be re-defined as Mixins - freeing up the precious inheritance hierarchy.
As the compiler already identifies calculated properties, I has hoping it wouldn't be that much work... :( Oh well.
brian Wed 20 Mar 2013
Promoted to ticket #2110 and assigned to brian
Seems like a pretty reasonable thing to add, so lets track it