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

Developer devteam.codafi at gmail.com
Fri Feb 26 12:32:43 CST 2016


What is your evaluation of the proposal?

I believe it is a well intended and certainly an interesting feature to have.

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

No, but not strongly.  Sure, there are cases where it would make more sense to use an "interface class" (a la Java) to implement an abstract data type, but I believe those kinds of design patterns are subsumed by protocols and Swift's general approach to designing data types in the large.  Even a language as dedicated to OO as Objective-C didn't need abstract classes, and where necessary, were simply implemented with macros declaring a one-line stub that throws an exception.  Even without macros, I don't believe the keystroke savings is enough to justify the inclusion of another keyword.

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

For the reasons above, I'm afraid not.

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

A quick reading.

~Robert Widmann

2016/02/26 13:11、Joe Groff via swift-evolution <swift-evolution at swift.org> のメッセージ:

> 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
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160226/d5ddeaaa/attachment.html>


More information about the swift-evolution mailing list