<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 Jan 19, 2016, at 2:46 PM, David Hart <<a href="mailto:david@hartbit.com" class="">david@hartbit.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">What effect would that have? Would the options still return a type (Selector) that is CustomStringConvertible or would it just be compiler magic?</div></div></blockquote><div><br class=""></div><div>Either way, we’ll return a Selector. The concern about “Selector(x.foo)” is that we would need special, ad hoc overload-resolution rules to decide between this magic syntax and other initializers of Selector. Making it a separate expression (“objc_selector(x.foo)”) or a special property on values of function type (“x.foo.selector”) eliminate that issue.</div><div><br class=""></div><div>We’d love to hear everyone’s thoughts on those approaches.</div><div><br class=""></div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">David.<br class=""><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 19 Jan 2016, at 23:43, Joe Groff 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">We discussed this proposal during our core team review meeting, and concerns were raised about the implementability of the proposed 'Selector(Type.method)' syntax. Producing the selector is something that can't quite be modeled as a real initializer, so the type checker would have to perform heroics to disambiguate a selector literal reference from a proper initializer call. We recommend reconsidering alternative syntactic forms for referencing the selector. Potential options include:<div class=""><br class=""></div><div class="">- A unique prefix identifier, such as `objc_selector(Type.method)`, as you had originally proposed, or</div><div class="">- Taking advantage of the fact that functions don't have members to ascribe special behavior to 'Type.method.objcSelector', or something like it.</div><div class=""><br class=""></div><div class="">-Joe</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jan 18, 2016, at 8:02 AM, Joe Groff 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><p style="word-wrap: break-word; margin: 1.3125em 0px; line-height: 1.3125em;" class=""><font color="#111111" face="Helvetica Neue, Helvetica, Arial, Verdana, sans-serif" class=""><span style="font-size: 14px;" class="">Hello Swift community,<br class=""><br class="">The review of “Referencing the Objective-C selector of a method” begins now and runs through January 23, 2016. The proposal is available here:<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0022-objc-selectors.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0022-objc-selectors.md</a><br class=""><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=""><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><br class=""><br class="">or, if you would like to keep your feedback private, directly to the review manager.<br class=""><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=""></span></font></p><div class=""><font color="#111111" face="Helvetica Neue, Helvetica, Arial, Verdana, sans-serif" class=""><span style="font-size: 14px;" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• What is your evaluation of the proposal?<br class=""></span></font></div><div class=""><font color="#111111" face="Helvetica Neue, Helvetica, Arial, Verdana, sans-serif" class=""><span style="font-size: 14px;" 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=""></span></font></div><div class=""><font color="#111111" face="Helvetica Neue, Helvetica, Arial, Verdana, sans-serif" class=""><span style="font-size: 14px;" 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=""></span></font></div><div class=""><font color="#111111" face="Helvetica Neue, Helvetica, Arial, Verdana, sans-serif" class=""><span style="font-size: 14px;" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br class=""></span></font></div><div class=""><font color="#111111" face="Helvetica Neue, Helvetica, Arial, Verdana, sans-serif" class=""><span style="font-size: 14px;" 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=""></span></font></div><p style="word-wrap: break-word; margin: 1.3125em 0px; line-height: 1.3125em;" class=""><font color="#111111" face="Helvetica Neue, Helvetica, Arial, Verdana, sans-serif" class=""><span style="font-size: 14px;" class="">More information about the Swift evolution process is available at<br class=""><br 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><br class=""><br class="">Thank you,<br class=""><br class="">-Joe<br class=""><br class="">Review Manager</span></font></p></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><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=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></div></div></div></blockquote></div><br class=""></body></html>