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

[Kurt Werle]

-1

On Tue, Jul 5, 2016 at 4:11 PM, Chris Lattner via swift-evolution <
swift-evolution at swift.org> wrote:

> Hello Swift community,
>
> The review of "SE-0117: Default classes to be non-subclassable publicly"
> begins now and runs through July 11. The proposal is available here:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0117-non-public-subclassable-by-default.md
>
> Reviews are an important part of the Swift evolution process. All reviews
> should be sent to the swift-evolution mailing list at
>
>         https://lists.swift.org/mailman/listinfo/swift-evolution
>
> 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?
>

I've used classes that were marked final that I wish were not.
I've never used a class that was not final that I wish was marked so.


>         * Is the problem being addressed significant enough to warrant a
> change to Swift?
>

I don't think the 'problem' described is a problem.

If you expose a class, you should think about how it might be subclassed.
In the very rare (and still too frequent) case when something should not be
subclassed, you should document it that way and explain why.


>         * Does this proposal fit well with the feel and direction of Swift?
>

I hope not.

Kurt
-- 
kurt at CircleW.org
http://www.CircleW.org/kurt/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160711/4b7184dd/attachment.html>