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

[Howard Lovatt]

 • What is your evaluation of the proposal?

I never use the feature and therefore wouldn't miss it. More importantly it
is confusing to both human and compiler and therefore should be removed.

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

Yes, it causes confusion and complicates the compiler.

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

Yes, it is a little used feature and part of the direction of Swift is to
focus on useful features and not be a collection of all possible ideas.

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

No experience of using the feature in either Swift or other languages.

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

I have followed the thread on Swift Evolution.


On Saturday, 6 February 2016, 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
>
>
> 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
>
>
> 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
>
> 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
>
>
> Thank you,
>
> -Joe
> Review Manager
>


-- 
  -- Howard.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160206/8bc6363c/attachment.html>