<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 9, 2017, at 8:12 AM, Gor Gyolchanyan via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class=""><div class=""><font color="#00afcd" class=""><br class=""></font>So I wonder if any of you have had any thoughts about what Swift's parentheses-related future (or evolutionary baggage) will be?<br class=""><font color="#00afcd" class=""><br class=""></font></div></div></blockquote><br class=""></div><div class="">I really wish swift used the concept of tuples **exclusively** for all purposes that involve parentheses, as well as dividing tuples into two categories:</div><div class="">- Bare tuples, which do not have labels.</div><div class="">- Rich tuples, which do.</div><div class="">As a consequence, here's a list of statements that would become true:</div><div class="">- All functions take exactly one parameter, which is a tuple.</div></div></div></blockquote><br class=""></div><div>That’s what we used to do. It caused problems with other language features (“inout" and “variadic" parameters were the two big ones, IIRC).</div><div><br class=""></div><div>- Dave Sweeris</div><br class=""></body></html>