<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div class=""><span style="background-color: rgba(255, 255, 255, 0);"><b>What is your evaluation of the proposal?</b><br class=""></span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);">I believe it is a well intended and certainly an interesting feature to have.</span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);"><b>Is the problem being addressed significant enough to warrant a change to Swift?</b><br class=""></span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);"><b><br></b></span></div><div class="">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.</div><div class=""><span style="background-color: rgba(255, 255, 255, 0);"><b><br></b></span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);"><b>Does this proposal fit well with the feel and direction of Swift?</b><br class=""></span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);"><b><br></b></span></div><div class="">For the reasons above, I'm afraid not.</div><div class=""><br></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);"><b>How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</b></span></div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">A quick reading.</div><br>~Robert Widmann</div><div><br>2016/02/26 13:11、Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> のメッセージ:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8">Hello Swift community,<br class=""><br class="">The review of “Abstract classes and methods” begins now and runs through March 4, 2016. The proposal is available here:<br class=""><br class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0026-abstract-classes-and-methods.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0026-abstract-classes-and-methods.md</a></blockquote><br class="">Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at<br class=""><br class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></blockquote><br class="">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:<br class=""><br class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">Proposal link:</blockquote><br class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0026-abstract-classes-and-methods.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0026-abstract-classes-and-methods.md</a></blockquote></blockquote><br class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">Reply text</blockquote><br class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">Other replies</blockquote><br class=""><b class="">What goes into a review?<br class=""></b><br class="">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:<br class=""><br class=""><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• What is your evaluation of the proposal?<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Is the problem being addressed significant enough to warrant a change to Swift?<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Does this proposal fit well with the feel and direction of Swift?<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br class=""></div><div class=""><br class=""></div>More information about the Swift evolution process is available at:<br class=""><br class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><a href="https://github.com/apple/swift-evolution/blob/master/process.md" class="">https://github.com/apple/swift-evolution/blob/master/process.md</a></blockquote><br class="">Thank you,<br class=""><br class="">-Joe<br class="">Review Manager</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>