<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Sorry for wrecking the threading, but any chance we could change the syntax to:</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">let (x myX: Int, y myY: Int) = ...</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">That would ensure the identifier after the colon was always treated as a type. I suppose if you wanted to infer the type, it'd be:</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);">let (x myX, y myY) = ...</span><br><br><div>-- </div><div>Brent Royal-Gordon</div>Sent from my iPhone</div><div><br>On May 5, 2017, at 12:04 AM, Adrian Zubarev via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div>If we ban reordering now, than I don’t see choosing different names in tuple destructuring as a strong argument of allowing labels there <code>let (x: a, y: b)</code>. They’re literally the same as one would write comments inside the destructured tuple <code>let (/* my x */ x, /* my y*/ y)</code>.</div></blockquote></body></html>