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

[Adrian Kashivskyy]

> What is your evaluation of the proposal?

-1. While I believe abstract methods can be a great addition for dealing with contract-like constructs in object-oriented languages, they seem out-of-place in Swift, which is a protocol-oriented language. Adding abstract methods to Swift would encourage lazy developers to use them instead of protocols and value types. 

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

Yes.

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

No. I believe it doesn't fit well in the direction Swift is taking.

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

Yes, PHP. While I must say that abstract classes and methods were a common and powerful tool in PHP, they do not fit well in Swift, which offers a much more powerful alternative – protocols.

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

A quick reading of the proposal document.


Pozdrawiam – Regards,
Adrian Kashivskyy

> Wiadomość napisana przez Joe Groff via swift-evolution <swift-evolution at swift.org> w dniu 26.02.2016, o godz. 19:11:
> 
> 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

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