<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class="">On Mar 31, 2017, at 10:29 AM, Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></blockquote><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hello Swift community, </div><div class=""><br class=""></div><div class="">The second review of "SE-0160: Limiting @objc inference" begins now and runs through April 2, 2017. The proposal is available here:</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0160-objc-inference.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0160-objc-inference.md</a></div><div class=""><br class=""></div><div class="">Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at:</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></div><div class=""><br class=""></div><div class="">or, if you would like to keep your feedback private, directly to the review manager. </div><div class=""><br class=""></div><div class=""><b class="">What goes into a review?</b></div><div class=""><br class=""></div><div 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:</div><div class=""><br class=""></div><div class="">* What is your evaluation of the proposal?</div><div class="">* Is the problem being addressed significant enough to warrant a change to Swift?</div><div class="">* Does this proposal fit well with the feel and direction of Swift?</div><div class="">* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</div><div class="">* How much effort did you put into your review? A glance, a quick reading, or an in-depth study? </div><div class=""><br class=""></div><div class=""><b class="">More information about the Swift evolution process is available at:</b></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/apple/swift-evolution/blob/master/process.md" class="">https://github.com/apple/swift-evolution/blob/master/process.md</a></div><div class=""> </div><div class="">Thanks!</div><div class=""><br class=""></div><div class="">-Chris Lattner</div><div class="">Review Manager</div><div class=""><br class=""></div><div class=""><br class=""></div></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""><div class="">+1. We may need to have a native implementation of the ‘dynamic’ keyword sometime in the future, and we’re locked out of doing that if we don’t get rid of the implied @objc now.</div><div class=""><br class=""></div><div class="">Charles</div><div class=""><br class=""></div></body></html>