<div dir="ltr"><span style="font-size:12.8px">* What is your evaluation of the proposal?</span><div>In theory, it seems like a great idea, but I fear that it will be one of those small changes that have disastrous effects on migrating code to Swift 4. There will likely be a ton of confusing errors and warnings that amount to "just add @objc to everything". Where there won't be errors or warnings, I can imagine that behavior could change in ways that most people can't predict.</div><div><br style="font-size:12.8px"><span style="font-size:12.8px">* Is the problem being addressed significant enough to warrant a change to Swift?</span></div><div>A 5% reduction in binary size is significant, and an issue that Swift is certainly running into. However I suspect that there are other ways to address this.</div><div><br style="font-size:12.8px"><span style="font-size:12.8px">* Does this proposal fit well with the feel and direction of Swift?</span></div><div>Yes.</div><div><br style="font-size:12.8px"><span style="font-size:12.8px">* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</span></div><div>N/A</div><div><br style="font-size:12.8px"><span style="font-size:12.8px">* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span><br></div><div><span style="font-size:12.8px">Read through the proposal.</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 21, 2017 at 11:03 PM, Chris Lattner via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Swift community,<br>
<br>
The review of "SE-0160: Limiting @objc inference" begins now and runs through March 28. The proposal is available here:<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0160-objc-inference.md" rel="noreferrer" target="_blank">https://github.com/apple/<wbr>swift-evolution/blob/master/<wbr>proposals/0160-objc-inference.<wbr>md</a><br>
<br>
Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at:<br>
<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>
<br>
or, if you would like to keep your feedback private, directly to the review manager.<br>
<br>
<br>
What goes into a review?<br>
<br>
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>
<br>
* What is your evaluation of the proposal?<br>
* Is the problem being addressed significant enough to warrant a change to Swift?<br>
* Does this proposal fit well with the feel and direction of Swift?<br>
* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
<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>