> If base classes were only allowed to be used in inheritance and couldn't be parameters, generics, etc then that would force users to create base classes and public interfaces in pairs and would decouple their names and by writing the public interface down as its own thing developers would be more likely to focus on that design.
I agree and like this principle, however, but what would be the difference between the base class and a mixin class then?
I agree and like this principle, however, but what would be the difference between the base class and a mixin class then?