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

[Brent Royal-Gordon]

> 	* What is your evaluation of the proposal?

I'm conflicted.

If there is even the slightest chance that a future version of Swift will ever add placeholder-based currying like `foo(1, bar: _)`, I strongly favor using an underscore-based syntax for this feature now. A placeholder-based currying syntax is a strict superset of this proposal's capabilities, so there's no reason to end up supporting three syntaxes; we can introduce the most sorely needed subset first and then make it more powerful later.

If there is absolutely no chance that placeholder-based currying will be added, even in Swift 4 or later, then I am in favor of this proposal.

> 	* Is the problem being addressed significant enough to warrant a change to Swift?

On the whole, yes. It's definitely an annoyance that you can't always access the method variant you need.

> 	* Does this proposal fit well with the feel and direction of Swift?

Yes. It turns a common convention into running code.

> 	* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

I don't really have any relevant experience. I haven't worked with many languages that supported both overloading and method references.

> 	* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

I've followed and participated in the thread, and spent a day or two thinking about my review before I wrote it.

-- 
Brent Royal-Gordon
Architechies