[swift-evolution] [Review] SE-0029 Remove implicit tuple splat behavior from function applications

[Patrick Gili]

> On Feb 5, 2016, at 1:12 PM, Joe Groff via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hello Swift community,
> 
> The review of “Remove implicit tuple splat behavior from function applications” begins now and runs through February 9, 2016. The proposal is available here:
> 
> https://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md <https://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.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. When replying, please try to keep the proposal link at the top of the message:
> 
> Proposal link:
> 
> http://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md <http://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md>
> 
> Reply text
> 
> Other replies
> 
> 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?

I do not use tuple splatting in Swift. Thus, if removing it will contribute to cleaning up the language and the compiler, then I support the change.

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

Sometimes we have to take a step backwards before taking two steps forward. We heard multiple proposals to better support the notion of tuple splatting during the debate following this proposal. However, it strikes me that none of these proposals can happen until the existing tuple splatting feature has been removed. Thus, I think it significant to progress.

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

Yes, for reasons I have already stated.

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

I have never seen or used tuple splatting in any language. However, I have used array splatting in Ruby, which I found very useful on occasion.

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

I read the proposal and the debate following the proposal very carefully.

> 
> 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/20160207/9c98c874/attachment.html>