[swift-evolution] A Comprehensive Rethink of Access Levels in Swift

Tino Heth 2th at gmx.de
Tue Feb 28 09:27:19 CST 2017

> as ‘closed’ is a rare niche case.

If there is agreement on the importance of closed, imho we shouldn't even need variants of final:
You could already build the required class hierarchies if the restriction that a subclass can't have higher visibility as its parent is lifted.

Imho this should be done anyways, and then you could simply define an internal baseclass with "public final" subclasses.

More information about the swift-evolution mailing list