<div dir="ltr"><div style="font-size:13px"><span style="white-space:pre-wrap">        </span>• What is your evaluation of the proposal?</div><div style="font-size:13px">+1</div><div style="font-size:13px"><span style="white-space:pre-wrap">        </span>• Is the problem being addressed significant enough to warrant a change to Swift?<br></div><div style="font-size:13px">Yes. Though I am in favor of thinking about functions as maps from tuple to tuple, the current behavior has too many nuanced wrinkles.</div><div style="font-size:13px"><span style="white-space:pre-wrap">        </span>• Does this proposal fit well with the feel and direction of Swift?<br></div><div style="font-size:13px">Yes</div><div style="font-size:13px"><span style="white-space:pre-wrap">        </span>• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></div><div style="font-size:13px">errr… yes?</div><div style="font-size:13px"><span style="white-space:pre-wrap">        </span>• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></div><div style="font-size:13px">I have followed the discussion, commented previously, and have both used and explained the behavior being changed.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 7, 2016 at 11:23 AM, Patrick Gili via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><span class=""><blockquote type="cite"><div>On Feb 5, 2016, at 1:12 PM, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div style="word-wrap:break-word">Hello Swift community,<br><br>The review of “Remove implicit tuple splat behavior from function applications” begins now and runs through February 9, 2016. The proposal is available here:<br><br><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md</a></blockquote><div><br>Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at<br><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a></div></blockquote><div><br>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:<br><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>Proposal link:</div><div><br></div><div><a href="http://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md" target="_blank">http://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md</a></div><div><br></div><div>Reply text</div><div><br></div><div>Other replies</div><div><br></div></blockquote><div><b>What goes into a review?<br></b><br>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:<br><br><div><span style="white-space:pre-wrap">        </span>• What is your evaluation of the proposal?<br></div></div></div></div></blockquote><div><br></div></span><div>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.</div><span class=""><br><blockquote type="cite"><div><div style="word-wrap:break-word"><div><div><span style="white-space:pre-wrap">        </span>• Is the problem being addressed significant enough to warrant a change to Swift?<br></div></div></div></div></blockquote><div><br></div></span><div>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.</div><span class=""><br><blockquote type="cite"><div><div style="word-wrap:break-word"><div><div><span style="white-space:pre-wrap">        </span>• Does this proposal fit well with the feel and direction of Swift?<br></div></div></div></div></blockquote><div><br></div></span><div>Yes, for reasons I have already stated.</div><span class=""><br><blockquote type="cite"><div><div style="word-wrap:break-word"><div><div><span style="white-space:pre-wrap">        </span>• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></div></div></div></div></blockquote><div><br></div></span><div>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.</div><span class=""><br><blockquote type="cite"><div><div style="word-wrap:break-word"><div><div><span style="white-space:pre-wrap">        </span>• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></div></div></div></div></blockquote><div><br></div></span><div>I read the proposal and the debate following the proposal very carefully.</div><br><blockquote type="cite"><div><span class=""><div style="word-wrap:break-word"><div><div><br></div>More information about the Swift evolution process is available at<br><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><a href="https://github.com/apple/swift-evolution/blob/master/process.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a></div></blockquote><div><br>Thank you,<br><br>-Joe<br>Review Manager</div></div></span><span class="">_______________________________________________<br>swift-evolution mailing list<br><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></span></div></blockquote></div><br></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>