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

[Javier Soto]

What is your evaluation of the proposal?
Strong +1. The syntax is clear and obvious, without looking at
documentation, one could almost guess it, and that's always great.

• Is the problem being addressed significant enough to warrant a change to
Swift?
Yup! Using objective-c APIs is still the bread and butter in Apple's
platforms, where a lot of Swift code is written. Stringly-typed selectors
are incredibly fragile. The target-selector pattern will still feel a bit
foreign in Swift, but this will at least make it look like we're passing a
partially-applied function.

• Does this proposal fit well with the feel and direction of Swift?
Yes, particularly with the proposed syntax to name any function.

• How much effort did you put into your review? A glance, a quick reading,
or an in-depth study?
I followed the discussion on the topic prior to the proposal these past
weeks, and read the proposal from begging to end.
On Mon, Jan 18, 2016 at 10:21 AM Félix Cloutier <swift-evolution at swift.org>
wrote:

> # What is your evaluation of the proposal?
>
> I support it.
>
> # Is the problem being addressed significant enough to warrant a change to
> Swift?
>
> One great advantage of being able to name a selector from a method is that
> tools can tell that some method from some class is being used as a
> callback. It can't tell that just from a selector string. This will be
> useful for refactoring tools.
>
> I think that selectors are going to die a very slow death, so we might as
> well have decent support for them.
>
> # Does this proposal fit well with the feel and direction of Swift?
>
> I guess?
>
> # If you have you used other languages or libraries with a similar
> feature, how do you feel that this proposal compares to those?
>
> Selectors are pretty unique to Objective-C.
>
> # How much effort did you put into your review? A glance, a quick reading,
> or an in-depth study?
>
> I read the proposal and was already convinced. I followed a little bit of
> discussion and everything looked good.
>
>
> Félix
>
> Le 18 janv. 2016 à 11:02:27, Joe Groff via swift-evolution <
> swift-evolution at swift.org> a écrit :
>
> Hello Swift community,
>
> The review of “Referencing the Objective-C selector of a method” begins
> now and runs through January 23, 2016. The proposal is available here:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0022-objc-selectors.md
>
> Reviews are an important part of the Swift evolution process. All reviews
> should be sent to the swift-evolution mailing list at
>
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
> or, if you would like to keep your feedback private, directly to the
> review manager.
>
>
> *What goes into a review?*
> 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:
>
> • What is your evaluation of the proposal?
> • Is the problem being addressed significant enough to warrant a change to
> Swift?
> • Does this proposal fit well with the feel and direction of Swift?
> • If you have you used other languages or libraries with a similar
> feature, how do you feel that this proposal compares to those?
> • How much effort did you put into your review? A glance, a quick reading,
> or an in-depth study?
>
> More information about the Swift evolution process is available at
>
> https://github.com/apple/swift-evolution/blob/master/process.md
>
> Thank you,
>
> -Joe
>
> Review Manager
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
-- 
Javier Soto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160118/dec23cc0/attachment.html>