Move default aspect function implementations from interfaces to concrete classes #354
Labels
refactoring
This requires refactoring existing code
standardization
Concerns conventions that should be strongly followed in mods
I think it would be better to declare the default implementations of aspect functions in the classes implementing the aspects instead of the aspect interfaces. The concern with default functions was reusability, but having them implicitly copied from the interface could be confusing. Instead of having the default functions implicitly copied, writing this code would at least make it clearer where they came from:
Because interface methods have always been copied from the start, this is a only change in convention instead of a change in the way the OOP system works.
The text was updated successfully, but these errors were encountered: