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

[Alsey Miller]

Ditto. Also I believe this goes against the spirit of Protocol Oriented Programming that Swift is trying to push.

> What is your evaluation of the proposal?
> 
> -1. The examples are not compelling enough. The only value currently, that I see at least, is the ability to require a specific storage mechanism for properties and to provide default values for all implementations of those properties.
> 
> Is the problem being addressed significant enough to warrant a change to Swift?
> 
> Maybe, but I believe updates to protocols are the better path.
> 
> Does this proposal fit well with the feel and direction of Swift?
> 
> No.
> 
> If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
> 
> Yes, such as C++ and C#. In the vast majority of cases, the usage seemed to break down into two basic categories: mixins and interfaces. I don't believe this proposal really addresses either of those use cases well.
> 
> How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
> 
> A quick reading.
> 
> -David
> 
> 
> > On Feb 26, 2016, at 10:11 AM, Joe Groff via swift-evolution<swift-evolution at swift.org>wrote:
> > 
> > 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<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<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<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<https://github.com/apple/swift-evolution/blob/master/process.md>
> > Thank you,
> > 
> > -Joe
> > Review Manager
> > _______________________________________________
> > swift-evolution mailing list
> > swift-evolution at swift.org
> > https://lists.swift.org/mailman/listinfo/swift-evolution
> 
> 
>  


	Coleman,





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