[swift-evolution] [Review] Naming Functions with Argument Labels

[Nathan de Vries]

> On Jan 14, 2016, at 5:50 PM, Douglas Gregor <dgregor at apple.com> wrote:
> 
> 
>> On Jan 13, 2016, at 4:36 PM, Nathan de Vries via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 
>> Hi Joe,
>> 
>> Do you have a plan for selecting between class and instance methods with the same name?
> 
> Excellent question! Swift’s overload resolution has some built-in preferences for picking static methods when referencing based on a metatype and for picking instance methods when referencing based on an instance, e.g.,
> 
> class X {
>   static func f0() -> Int { return 0 }
>   func f0() -> String { return "" }
> }
> 
> let fn1 = X.f0 // () -> Int
> let x = X()
> let fn2 = x.f0 // () -> String
> 
> 
> So one might have to conjure up an instance to force the instance method, or use type context to force the issue:
> 
> let fn3: (X) -> () -> String = X.f0
> 
> but it can be done without extra syntax.

From what I understand, the above will only work if the method names are the same but the type signature is different, otherwise you'd need to conjure up an instance. Is that correct?

Would it be strange to use X.f0 to refer to the instance method, and X.self.x0 to refer to the static method?

—Nathan


>>> On Jan 14, 2016, at 4:16 AM, Joe Groff via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>> 
>>> Hello Swift community,
>>> 
>>> The review of "Naming Functions with Argument Labels" begins now and runs through January 10th. The proposal is available here:
>>> 
>>> 	https://github.com/apple/swift-evolution/blob/master/proposals/0021-generalized-naming.md <https://github.com/apple/swift-evolution/blob/master/proposals/0018-flexible-memberwise-initialization.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,
>>> 
>>> -Joe
>>> Review Manager
>>> 
>>> _______________________________________________
>>> swift-evolution mailing list
>>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
>> 
>>  _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160114/1d7de7aa/attachment.html>