<div dir="ltr">-0.5, I agree with Andrew Bennett and Brent Roayal-Gordon.<div><br></div><div>I use this functionality a lot, which means I've had to experience and navigate around the inconsistencies and bugs of the current implementation, but removing this functionality all together would leave us with a significantly less capable/expressive language. </div><div><br></div><div>IMHO this (albeit buggy) aspect of the language is what allows one of its key must-have-features, namely being able to work with generic higher order functions in an (almost) acceptable way.<div><br><div>Suddenly loosing the ability to write and use higher order generic functions (eg generic function composition, generic function application, without having to special-case for every arity etc) would severely bloat my code and decrease my productivity.</div><div><br></div><div>I was delighted to see Swift resurfacing these simple yet powerful and, really, basic tools of programming. Now I'm not sure what to expect. I fear that I will have to seriously consider moving back to using C++ templates : ( or perhaps resort to always use only a single tuple parameter, like eg this:</div><div><div>func f(args: (T, T)) -> T { ... }</div><div>instead of this:</div><div>func f(a: T, b: T) -> T { ... }</div><div>How else would I be able to do simple stuff like composing them etc?</div><div><br></div><div>/Jens</div></div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 9, 2016 at 10:13 AM, Jerome ALVES 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">Hello,<div><br></div><div>I use this feature to make generic "weak target actions" like this :</div><div><br></div><div><br></div><div><font face="Menlo">func weakTarget<T, S: AnyObject>(target: S, action: S -> (T -> Void)) -> (T -> Void) {<br> return { [weak target] (input: T) -> Void in<br> guard let target = target else { return }<br> return action(target)(input)<br> }<br>}<br><br>class Target {</font></div><div><span style="font-family:Menlo"> init() {}</span></div><div><font face="Menlo"> func printHello(firstName: String, lastName: String) {<br> print("Hello \(firstName) \(lastName) !")<br> }<br>}<br><br>class Receiver {<br></font><div><span style="font-family:Menlo"> init() {}</span></div><font face="Menlo"> var printSomething: ((String, String) -> Void)? = nil<br>}<br><br>var aTarget: Target? = Target()<br>let aReceiver = Receiver()<br><br>aReceiver.printSomething = weakTarget(aTarget!, action: Target.sayHello)<br><br>aReceiver.</font><span style="font-family:Menlo">printSomething</span><font face="Menlo">?("Jérôme", "Alves") // => "Hello Jérôme Alves !"<br><br>a = nil</font></div><div><font face="Menlo"><br>aReceiver.printSomething?("Jérôme", "Alves") // => aReceiver.printSomething still has a value, but it does nothing<br><br></font></div><div><br></div><div>As you can see, if you call weakFunc() with a func which has multiple arguments, the T generic will be a tuple and I guess this is thanks to this "implicit tuple splat" feature but I'm not sure.</div><div>So can someone enlighten me ? Will this code continue to work if this proposal is approved ?</div><div><br></div><div><br><div><blockquote type="cite"><div><div class="h5"><div>Le 5 févr. 2016 à 19:12, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> a écrit :</div><br></div></div><div><div><div class="h5"><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><span style="white-space:pre-wrap"> </span>• Is the problem being addressed significant enough to warrant a change to Swift?<br></div><div><span style="white-space:pre-wrap"> </span>• Does this proposal fit well with the feel and direction of Swift?<br></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><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><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></div></div><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></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><br clear="all"><div><br></div>-- <br><div class="gmail_signature">bitCycle AB | Smedjegatan 12 | 742 32 Östhammar | Sweden<br><a href="http://www.bitcycle.com/" target="_blank">http://www.bitcycle.com/</a><br>Phone: +46-73-753 24 62<br>E-mail: <a href="mailto:jens@bitcycle.com" target="_blank">jens@bitcycle.com</a><br><br></div>
</div>