<div dir="ltr">Would using backticks work? If we used them here and in the closure-from-function syntax, it would be somewhat consistent and–hopefully–not terribly ambiguous.<div><br></div><div>TJ</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 19, 2016 at 9:20 PM, Pj Fechner 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"><div dir="ltr"><p style="margin:0px;line-height:normal;font-family:Helvetica"><span style="white-space:pre-wrap"> </span>To avoid beating a dead horse, I’ll sum up my sentiments by saying that it seems clear Selectors as they currently exist are a fairly outdated and confusing approach for Objective-C and even more so for Swift.</p>
<p style="margin:0px;line-height:normal;font-family:Helvetica;min-height:13px"><span></span><br></p>
<p style="margin:0px;line-height:normal;font-family:Helvetica"><span><span style="white-space:pre-wrap"> </span>When learning or developing a new paradigm, it’s very easy to bring the baggage of the old philosophy into the new approach. While adding the ability to initialize Selectors with a function/closure is certainly an improvement, (and possibly should be implemented regardless), it also seems to be a very non-Swift solution to the problems Selectors are trying to solve. </span></p>
<p style="margin:0px;line-height:normal;font-family:Helvetica;min-height:13px"><span></span><br></p>
<p style="margin:0px;line-height:normal;font-family:Helvetica"><span><span style="white-space:pre-wrap"> </span>If Classes like UIGestureRecognizers were being written today without Selectors already in existence, I find it hard to believe they would be created when a function reference or closure/block would be more understandable and reliable in most cases. </span></p>
<p style="margin:0px;line-height:normal;font-family:Helvetica;min-height:13px"><span></span><br></p>
<p style="margin:0px;line-height:normal;font-family:Helvetica"><span><span style="white-space:pre-wrap"> </span>With that in mind, the more forward thinking and swift-like approach appears to be rewriting or replacing the APIs that use selectors to use newer strategies to accomplish the same thing. There may be edge cases where the dynamism and flexibility of Selectors are needed or desired, but this is by no means the norm and should only be considered on a case by case basis. </span></p>
<p style="margin:0px;line-height:normal;font-family:Helvetica;min-height:13px"><span></span><br></p>
<p style="margin:0px;line-height:normal;font-family:Helvetica"><span>In Summation:</span></p>
<p style="margin:0px;line-height:normal;font-family:Helvetica;min-height:13px"><span></span><br></p>
<ul><span class="">
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span><span><i>What is your evaluation of the proposal?</i></span></li>
</span><ul>
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span><span>Possibly necessary, but it seems to be a workaround, not a solution</span></li>
</ul>
</ul>
<p style="margin:0px;line-height:normal;font-family:Helvetica;min-height:13px"><span></span><br></p>
<ul><span class="">
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span><span><i> Is the problem being addressed significant enough to warrant a change to Swift?</i></span></li>
</span><ul>
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span><span>Yes. Whether with this solution or another, it is a serious oversight of the current platform</span></li>
</ul>
</ul>
<p style="margin:0px;line-height:normal;font-family:Helvetica;min-height:13px"><span></span><br></p>
<ul><span class="">
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span><span><i>Does this proposal fit well with the feel and direction of Swift?</i></span></li>
</span><ul>
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span><span>Direction, yes. Feel, no. </span></li>
</ul>
</ul>
<p style="margin:0px;line-height:normal;font-family:Helvetica;min-height:13px"><span></span><br></p>
<ul><span class="">
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span><span><i>If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</i></span></li>
</span><ul>
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span><span>I haven’t used another language that uses a Selector-like approach. Yet another reason why it should be changed :)</span></li>
</ul>
</ul>
<p style="margin:0px;line-height:normal;font-family:Helvetica;min-height:13px"><span></span><br></p>
<ul><span class="">
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span><span>How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span></li>
</span><ul>
<li style="margin:0px;line-height:normal;font-family:Helvetica"><span style="line-height:normal"></span>Roughly 7 out of 10.</li>
</ul></ul></div>
<br>_______________________________________________<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/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>