<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span style="background-color: rgba(255, 255, 255, 0);"><br><br></span><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">On 26 Feb 2016, at 19:11, Joe Groff via swift-evolution <<a dir="ltr" href="mailto:swift-evolution@swift.org" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="1">swift-evolution@swift.org</a>> wrote:<br></span></font></blockquote><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></font></blockquote><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);"> • What is your evaluation of the proposal?<br></span></font></blockquote><span style="background-color: rgba(255, 255, 255, 0);"><br>-1. I'm strongly against this proposal because they are already language features that provide similar benefits. Even if Swift is a multi-paradigm language, it has always meshed together orthogonal concepts: functional + oop + systems. Whereas in a his case, the proposal suggests adding a different syntax for something that can almost be completely expressed with protocols and protocol extensions.<br><br></span><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);"> • Is the problem being addressed significant enough to warrant a change to Swift?<br></span></font></blockquote><span style="background-color: rgba(255, 255, 255, 0);"><br>As POP can already provide similar behaviour without subclassing, I'd say the problem is pretty much non-existent.<br><br></span><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);"> • Does this proposal fit well with the feel and direction of Swift?<br></span></font></blockquote><span style="background-color: rgba(255, 255, 255, 0);"><br>No. I believe it goes contrary to the philosophy and paradigms of Swift as I understand them.<br><br></span><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);"> • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></span></font></blockquote><span style="background-color: rgba(255, 255, 255, 0);"><br>Yes, Java and C#. Abstract classes were useful in those languages, but fairly rarely used (as far as I'm concerned). And we now have protocol extensions to do the same.<br><br></span><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);"> • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></span></font></blockquote><span style="background-color: rgba(255, 255, 255, 0);"><br>In-depth reading, followed he discussion.<br>_______________________________________________<br>swift-evolution mailing list<br><a dir="ltr" href="mailto:swift-evolution@swift.org" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="2">swift-evolution@swift.org</a><br><a dir="ltr" href="https://lists.swift.org/mailman/listinfo/swift-evolution" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="3">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span></div></body></html>