You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Kotlin has default interface implementations, would it be better (or possible) to implement any of these as interfaces instead of abstract classes?
@damianw Interfaces cannot have state, cannot implement members of Any (namely hashCode, equals and toString). Also when two unrelated interfaces declare the same member it burdens an implementor of them both to have an override to select which one to use.
Making abstract mutable collections become interfaces would render impossible to reuse JDK implementations.
Discussions about the Read-only and mutable abstract collections will be held here.
The text was updated successfully, but these errors were encountered: