<div dir="ltr">Hi plx,<div><br></div><div>Please take a look at my proposal:</div><div> <a href="http://comments.gmane.org/gmane.comp.lang.swift.evolution/5334">http://comments.gmane.org/gmane.comp.lang.swift.evolution/5334</a><br></div><div><br></div><div>It introduces tuple operators capable of doing many of the things you suggest.</div><div><br></div><div>In case you missed it, you can currently do unlabel/relabel like this:</div><div><p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="color:rgb(187,44,162)"><br></span></p><p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="color:rgb(187,44,162)"> let</span> m = (a: <span style="color:rgb(39,42,216)">1</span>, b: <span style="color:rgb(39,42,216)">2</span>) <span style="color:rgb(187,44,162)">as</span> (<span style="color:rgb(112,61,170)">Int</span>,<span style="color:rgb(112,61,170)">Int</span>) <span style="color:rgb(187,44,162)">as</span> (c: <span style="color:rgb(112,61,170)">Int</span>, d: <span style="color:rgb(112,61,170)">Int</span>)</p></div><div><br></div><div>It's just not as concise.</div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 7, 2016 at 1:01 AM, plx 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"><div>+1.</div><div><br></div><div>I’m in the camp of people who would want an explicit version of this to make an eventual return, ideally as part of a broader suite of "tuple-manipulation operations”.</div><div><br></div><div>In such a proposal I’d hope to see, for example, splatting, but also compiler-assistance for things like:</div><div><br></div><div>- tuple-concatenation: (a,b)##(c,d) => (a,b,c,d)</div><div>- tuple-flattening: (a,(b,(c,d))#flatten => (a,b,c,d)</div><div>- tuple-rearrange: (a,b,c,d)#rearrange(($2,$1),($4,$3)) => ((b,a),(d,c))</div><div>- tuple-relabel: (a,b,c,d)#relabel(foo:,bar:,baz:,qux:) => (foo: a, bar: b, baz: c, qux: d)</div><div>- tuple-unlabel: (foo: a, bar: b, baz: c, qux: d)#unlabel => (a,b,c,d)</div><div><br></div><div>…with the above as examples of the kinds of operations, and not really the syntax; whatever’s chosen, it ought to be possible — although perhaps not *advisable* — to write e.g.:</div><div><br></div><div>// plz use a dedicated “zip4" in real life:</div><div>for (a,b,c,d) in zip(zip(as,bs),zip(cs,ds)).lazy.map(#flatten) { … }</div><div><br></div><div>…but that’s enough about tuple operations for now, I just wanted to illustrate some of the operations that be supported. </div><div><br></div><div>Moving on, as I’m in favor of the proposal as it stands, I don’t have anything to contribute to the proposal itself.</div><div><br></div><div>That said, I *do* think it’s unwise to infer too much from low rates of use for implicit tuple splatting at this time; it seems a little unfair to treat “this feature doesn’t work" and "no one seems to be using it” as *independent* variables, here.</div><div><br></div><div>As one such example, I implemented a large amount of a largely-declarative, combinator-ish “JSON parsing” library that would’ve made heavy use of tuple-splatting *if* it actually worked, but as splatting wound up seeming troublesome I gave up trying to use splatting. </div><div><br></div><div>FWIW not having splatting doesn’t change the size of the *library* code very much, but makes each site-of-use substantially-larger.</div><br><div><blockquote type="cite"><div><div class="h5"><div>On Feb 5, 2016, at 12: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><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><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>