[Review #2] SE-0117: Default classes to be non-subclassable publicly&References=2C9B4C5A-52C2-4E0E-8B9E-6E5444629D85@apple.com&In-reply-to=2C9B4C5A-52C2-4E0E-8B9E-6E5444629D85@apple.com

I have no concerns intrinsically to the behavior discussed but rather to
the complexity that this brings. Creating another type of access control
and possibly keyword just adds complexity to an already fairly complex
language. I’d probably be more onboard if it was merely final by default
for that reason alone.

Hello Swift community,

The second review of "SE-0117: Default classes to be non-subclassable

publicly" begins now and runs through July 22. The proposal is available

Reviews are an important part of the Swift evolution process. All reviews

should be sent to the swift-evolution mailing list at


or, if you would like to keep your feedback private, directly to the

review manager.

What goes into a review?

The goal of the review process is to improve the proposal under review

through constructive criticism and contribute to the direction of Swift.
When writing your review, here are some questions you might want to answer
in your review:

* What is your evaluation of the proposal?
* Is the problem being addressed significant enough to warrant a change

to Swift?

* Does this proposal fit well with the feel and direction of Swift?
* If you have used other languages or libraries with a similar feature,

how do you feel that this proposal compares to those?

* How much effort did you put into your review? A glance, a quick

reading, or an in-depth study?

More information about the Swift evolution process is available at


Thank you,

-Chris Lattner
Review Manager