<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">* What is your evaluation of the proposal?<br></blockquote><div>+1 in intent and -1 in detail.</div><div><br></div><div>I think reducing the amount of magic helps make swift more powerful and easier to understand. This will force developers to add a few more `@objc` tokens, but the consistency will help in the long run.</div><div><br></div><div>The last section in "Source Compatibility" calls out a few problems, presents some possible solutions, but states that they are "Out of scope for this proposal". Given the depth of migration issues that this proposal is expected to incur, I think leaving out these details feels short-sighted. If this proposal is approved, when are the 'out of scope' behaviors decided?</div><div><br></div><div>A few specific opinions on the possibilities presented:</div><div>- I'd like a clearer explanation on how the inferred `dynamic` behavior would change. I would prefer @objc to always infer dynamic or never infer dynamic. Currently it's context dependent and confusing. </div><div>- I don't like forcing extension methods that are not `@objc` be flagged `final`. That seems heavy handed.</div><div>- I'd like to get over-rides in extensions working!</div><div><br></div><div>That said, I'm new here, and I'm a net +0. I trust a good choice will be made. <br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
* Is the problem being addressed significant enough to warrant a change to Swift?<br></blockquote><div>Yes<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
* Does this proposal fit well with the feel and direction of Swift?<br></blockquote><div>Yes </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></blockquote><div>No Experience</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></blockquote><div>In-depth study<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
More information about the Swift evolution process is available at:<br>
<a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank">https://github.com/apple/<wbr>swift-evolution/blob/master/<wbr>process.md</a><br>
<br>
Thanks!<br>
<br>
-Chris Lattner<br>
Review Manager<br>
______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</blockquote></div><br></div></div>