Re: [swift-users] Function overload resolution rules

2016-09-30 Thread Toni Suter via swift-users
I created a bug report here: https://bugs.swift.org/browse/SR-2810 Best regards, Toni > Am 30.09.2016 um 19:47 schrieb Mark Lacey : > >> >> On Sep 30, 2016, at 5:02 AM, Toni Suter via swift-users >> mailto:swift-users@swift.org>> wrote: >> >> Hi, >> >

Re: [swift-users] Function overload resolution rules

2016-09-30 Thread Mark Lacey via swift-users
> On Sep 30, 2016, at 5:02 AM, Toni Suter via swift-users > wrote: > > Hi, > > I am trying to get a better understanding of Swift's function overload > resolution rules. > As far as I can tell, if there are multiple candidates for a function call, > Swift favors > functions for which the lea

Re: [swift-users] Function overload resolution rules

2016-09-30 Thread Vladimir.S via swift-users
On 30.09.2016 15:02, Toni Suter via swift-users wrote: Hi, I am trying to get a better understanding of Swift's function overload resolution rules. As far as I can tell, if there are multiple candidates for a function call, Swift favors functions for which the least amount of parameters have bee

[swift-users] Function overload resolution rules

2016-09-30 Thread Toni Suter via swift-users
Hi, I am trying to get a better understanding of Swift's function overload resolution rules. As far as I can tell, if there are multiple candidates for a function call, Swift favors functions for which the least amount of parameters have been ignored / defaulted. For example: // Example 1 func