[swift-evolution] [Review] SE-0117: Default classes to benon-subclassable publicly

Brent Royal-Gordon brent at architechies.com
Wed Jul 13 08:41:06 CDT 2016

> On Jul 11, 2016, at 3:51 PM, Károly Lőrentey via swift-evolution <swift-evolution at swift.org> wrote:
> - Annoyance: People will need to remember to manually add an extra keyword to their public classes whenever they want to allow subclassing. People who want to always allow cross-module subclassing will always have to add the keyword. The extra work to do this would be annoying and pointless, and the proliferation of such additional keywords would make Swift needlessly wordy.

There will be no need for an *extra* keyword if we use a keyword that replaces `public`, like the proposed keywords or my preferred `open`. It would merely be a *different* keyword.

Brent Royal-Gordon

More information about the swift-evolution mailing list