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

Jeff Kelley slaunchaman at gmail.com
Wed Jan 13 12:58:24 CST 2016

> 	* What is your evaluation of the proposal?

As a developer using Swift in a large project, I’ve had a few situations where this proposal would have been useful. As the proposal states, you can always wrap the explicit call in a closure, but that’s more cumbersome and potentially not as efficient (I wonder if there’s a compiler optimization to replace the closure with the function it calls). To that end, I would love to see this in Swift.

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

I am by no means a compiler engineer, so I can’t speak to the level of effort to implement it compared to the benefit, but I do think it’s a clear benefit to Swift without a lot of impact on existing code, if any.

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

Yes. Incidentally, I’m already using this syntax in a book <https://pragprog.com/book/jkwatch2/developing-for-apple-watch-second-edition> I’m writing that uses Swift; I refer to methods like setTintColor(_:) all the time.

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

I’ve read the discussion on swift-evolution, read the final proposal on GitHub, and run into this problem in the “real world.”

Jeff Kelley

SlaunchaMan at gmail.com | @SlaunchaMan <https://twitter.com/SlaunchaMan> | jeffkelley.org <http://jeffkelley.org/>
> On Jan 13, 2016, at 12:16 PM, Joe Groff via swift-evolution <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:
> 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
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160113/5e6a16c6/attachment.html>

More information about the swift-evolution mailing list