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

[David Hart]

• What is your evaluation of the proposal?

I’ve known about the tuple splat feature but have never used it in my code or seen a real need for it. Therefore, if removing can simplify the language and the compiler, I’m all for it.

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

I believe so.

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

It does fit well with a desire to start simplifying or removing features which are rarely used.

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

I have used other functional languages which have that functionality, but I’ve always shed away from it because it made code harder to read.

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

I read the proposal in detail and read the discussion in the mailing list, so a fairly serious study.

> On 05 Feb 2016, at 19:12, 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?
> 	• 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 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
> https://lists.swift.org/mailman/listinfo/swift-evolution

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