<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 15, 2017, at 4:55 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="Singleton"><div class=""><div class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><div class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=""><div class=""><div style="word-wrap: break-word;" class=""><div class=""><blockquote type="cite" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><br class="Apple-interchange-newline">Agreed, it may be too late to correct this (certainly we can't outright remove it in Swift 4 if someone is using it for something important). However if it turns out that it really isn't used, then warning about it in 4 and removing it shortly after may be possible.</div></div></div></div></div></blockquote><div class=""><br class=""></div><div class="">And I think its difficult to make the parallel between the two. SE-0110 basically impacted everybody calling higher-order functions on Dictionary (+ more users from libraries like RxSwift), which makes an enormous proportion of the Swift community. On the other hand, despite the enormous amount of time I have sinked into learning, discussing and enjoying Swift, I never come upon the tuple element name syntax in patterns until Robert pointed to it out on twitter several weeks ago.</div></div></div></div></blockquote><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div></div></div><div style="word-wrap: break-word;" class=""><div class=""><div class="">By the way, I’m not attempting to deduce that nobody uses this feature by the fact I didn’t know about it. But I think it’s one interesting datapoint when comparing it to SE-0110.</div></div></div></blockquote><div class=""><br class=""></div><div class=""><br class=""></div></div></div></div><div class=""><div class=""><div class="gmail_quote"><div class="">SE-0110, **in retrospect**, has had impacts on a lot of users; prospectively, it was thought to be a minor change, even after review and acceptance.</div><div class=""><br class=""></div><div class="">Keep in mind that this proposed change would also eliminate inline tuple shuffle. For instance, the following code will cease to compile:</div><div class=""><br class=""></div><div class=""><div class="">let x = (a: 1.0, r: 0.5, g: 0.5, b: 0.5)</div><div class="">func f(color: (r: Double, g: Double, b: Double, a: Double)) {</div><div class=""> print(color)</div><div class="">}</div></div><div class="">f(color: x)</div><div class=""><br class=""></div><div class="">It is an open question how frequently this is used. But like implicit tuple destructuring, it currently Just Works(TM) and users may not realize they’re making use of the feature until it’s gone.</div></div></div></div><div class=""><div class=""><div class="gmail_quote"></div><br class="Apple-interchange-newline"></div></div></div></div></blockquote></div><br class=""><div class="">To (re)clarify, I was just talking about removing tuple element names from the tuple pattern grammar. This example doesn’t use tuple patterns, so it wouldn’t be affected. I’m not proposing removing tuple shuffles.</div><div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""></div></body></html>