<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 31, 2017, at 9:35 AM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">On Fri, Mar 31, 2017 at 10:29 AM, Chris Lattner via swift-evolution<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" 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="m_-5068865771146890679Apple-tab-span" style="white-space: pre-wrap;"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0160-objc-inference.md" target="_blank" class="">https://github.com/apple/<wbr class="">swift-evolution/blob/master/<wbr class="">proposals/0160-objc-inference.<wbr class="">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="m_-5068865771146890679Apple-tab-span" style="white-space: pre-wrap;"> </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank" class="">https://lists.swift.org/<wbr class="">mailman/listinfo/swift-<wbr class="">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></blockquote><div class=""><br class=""></div><div class="">I do think this current iteration is an improvement. I have to say, though, that I prefer Doug Gregor's spelling of `@implicitobjc` over `@objcMembers`. It think the former explains the feature a little better and also happens to be subjectively nicer-looking.</div></div></div></div></div></blockquote><div><br class=""></div>I think @objcMembers is more precise: it doesn’t imply that the class itself is @objc, just that the members are @objc.</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br class=""></div></body></html>