<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 20, 2016, at 7:39 PM, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.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=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jan 20, 2016, at 3:48 PM, Douglas Gregor 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=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jan 19, 2016, at 4:52 PM, Douglas Gregor 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=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jan 19, 2016, at 4:40 PM, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com" class="">jtbandes@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Is there a well-defined meaning for `#` ? </div></div></blockquote><div class=""><br class=""></div><div class="">Not yet.</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">What about #selector(x)?</div></div></blockquote><div class=""><br class=""></div><div class="">Objective-C selector formation is a *very* narrow feature to consider stealing one of our few underused sigils.</div></div></div></div></blockquote><div class=""><br class=""></div><div class="">Actually, this isn’t that much different from “#available”, in the sense that it’s a special, compiler-supported expression type for which we don’t want to necessarily steal a keyword. What do others think about “#selector”?</div></div></div></div></blockquote><br class=""></div><div class="">I think that #selector is workable and fits into the model - it would be simple to implement and not cause unnecessary complexity in the implementation.</div><div class=""><br class=""></div><div class="">That said, I’m in favor of x.selector, or #selector(x). The former seems more syntactically elegant if it is practical.</div></div></div></blockquote><br class=""></div><div>The latter gives us easy extensions like</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>#selector(getter: MyType.property)</div><div><div><span class="Apple-tab-span" style="white-space: pre;"> </span>#selector(setter: MyType.property)</div><div class=""><br class=""></div><div class="">#selector is sorta growing on me.</div><div class=""><br class=""></div></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br class=""></div><br class=""></body></html>