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

Alex Hoppen alex at ateamer.de
Sun Feb 7 08:57:52 CST 2016

+1 for removing implicit tuple splat.

I think this is a rarely used feature and would fit well in the Swift 3 goal of cleaning up the type system. I believe this would also solve some ambiguities that, IMO, cannot be properly solved, e.g.

func f(x: Any) {

func f(a: Int, _ b: Int) {
  print("Int, Int")

f(3,4) // Currently resolved as f(Int, Int)

let a = (3,4)
f(a) // Currently resolved as f(Int, Int)

f(a as Any) // Currently resolved as f(Any)

f((3,4)) // Currently ambigous expression

If tuple splatting is not remove, I think that there should be a consistent solution to resolving ambiguity in the example provided above (in particular I think that there shouldn’t be a difference between f(a) and f((3,4)). I already tried to solve this issue but am not going to put more effort into it until this proposal is decided.

- Alex

> On 05 Feb 2016, at 19:12, Joe Groff <jgroff at apple.com> 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-announce mailing list
> swift-evolution-announce at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce

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

More information about the swift-evolution mailing list