[swift-evolution] [Review] SE-0022: Referencing the Objective-C selector of a method

T.J. Usiyan griotspeak at gmail.com
Wed Jan 20 10:29:55 CST 2016


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.

TJ

On Tue, Jan 19, 2016 at 9:20 PM, Pj Fechner via swift-evolution <
swift-evolution at swift.org> wrote:

> 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.
>
>
> 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.
>
>
> 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.
>
>
> 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.
>
>
> In Summation:
>
>
>
>    - *What is your evaluation of the proposal?*
>       - Possibly necessary, but it seems to be a workaround, not a
>       solution
>
>
>
>    - * Is the problem being addressed significant enough to warrant a
>    change to Swift?*
>       - Yes. Whether with this solution or another, it is a serious
>       oversight of the current platform
>
>
>
>    - *Does this proposal fit well with the feel and direction of Swift?*
>       - Direction, yes. Feel, no.
>
>
>
>    - *If you have you used other languages or libraries with a similar
>    feature, how do you feel that this proposal compares to those?*
>       - I haven’t used another language that uses a Selector-like
>       approach. Yet another reason why it should be changed :)
>
>
>
>    - How much effort did you put into your review? A glance, a quick
>    reading, or an in-depth study?
>       - Roughly 7 out of 10.
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160120/c2e38e6c/attachment.html>


More information about the swift-evolution mailing list