[swift-evolution] [Review] SE-0022: Referencing the Objective-C selector of a method
erica at ericasadun.com
Tue Jan 19 19:12:24 CST 2016
The former seems more ObjCbridgish. The latter seems more Swiftish. While I prefer the aesthetics of the latter, the former seems to better call out the bridging semantics for anyone reading through code.
I guess I'd want to know whether there are or will be similar approaches for example, I dunno, pulling Foundation objects in (like objc_type(Dictionary)) and if so which approach would you use there?
-- E, who is probably rambling but hopes this adds something to weighing between the two
> On Jan 19, 2016, at 3:43 PM, Joe Groff via swift-evolution <swift-evolution at swift.org> wrote:
> 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:
> - A unique prefix identifier, such as `objc_selector(Type.method)`, as you had originally proposed, or
> - Taking advantage of the fact that functions don't have members to ascribe special behavior to 'Type.method.objcSelector', or something like it.
>> On Jan 18, 2016, at 8:02 AM, Joe Groff via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 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 <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 <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 <https://github.com/apple/swift-evolution/blob/master/process.md>
>> Thank you,
>> Review Manager
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution