> An abstract base class can expose private or internal abstract requirements
> to its implementation subclasses while exporting a different interface for
> external users.
I think what you want for this is real orthogonality of access rights (being
able to declare a method that can’t be called, but just overridden) — but I
fear this option died with „open“, and the topic is scorched earth for the next
years
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
