Sent from my iPad
On Jun 29, 2016, at 2:54 PM, John McCall via swift-evolution <[email protected]> wrote: >> On Jun 29, 2016, at 11:39 AM, Vladimir.S <[email protected]> wrote: >> How about `public(extensible)` ? > > Hmm. I started to work out an example with these as separate modifiers, and > I think I understand the need to combine them in some way. > > I wonder if just "extensible" would be good enough. It is a term that's used > in API descriptions. 'extensible' is a broad term. That has both advantages and disadvantages. An advantage is that it can be used to mean both 'subclassable' / 'inheritable' as well as 'overridable'. This would allow us to use a single keyword, while sealing methods by default in 'extensible' classes. A disadvantage is that is isn't immediately clear what kind of extensibility is provided - you just have to know what the keyword means in a specific context. Perhaps a larger disadvantage is that 'extensible' shares a root with 'extension' and all public classes are open to extension in Swift. -Matthew > > John. > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
