[swift-evolution] [Review] SE-0026 Abstract classes and methods

[Alsey Miller]

- What is your evaluation of the proposal?

I am against the proposal because I feel it goes against the Protocol Oriented Programming patterns found in the Swift Standard Library. Current protocol functionality can provide a solution for the given example. If a protocol property is not implemented, the compiler will not let you compile. 

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

No, protocols implement this functionality, but with a different syntax. There is no lacking or additional functionality this proposal provides.

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

No. It goes against protocol oriented programming. Furthermore, this is only for classes, structs are being excluded in this case. I feel that with most of the standard library being implemented as structs, this is not acceptable.

• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

Similar to C# or Java abstract classes. Not much to add here.

• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

In-depth study. I understand the proposer’s point of view, but I feel this is only a syntax change in the wrong direction. No new functionality is being provided that protocols don’t already have.

> Hello Swift community,
> 
> The review of “Abstract classes and methods” begins now and runs through March 4, 2016. The proposal is available here:
> 
> https://github.com/apple/swift-evolution/blob/master/proposals/0026-abstract-classes-and-methods.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. When replying, please try to keep the proposal link at the top of the message:
> 
> Proposal link:
> 
> https://github.com/apple/swift-evolution/blob/master/proposals/0026-abstract-classes-and-methods.md
> 
> Reply text
> 
> Other replies
> 
> What goes into a review?
> 
> The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine 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:
> 
> https://github.com/apple/swift-evolution/blob/master/process.md
> 
> Thank you,
> 
> -Joe
> Review Manager
> 
> 
>  


	Coleman,





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160229/645872b8/attachment.html>