<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">My answer to `inout` is to promote it to a full-fledged "storage class" (in C terminology) and allow normal variables to be `inout`.<div class="">This would immediately solve the problems with `inout` being a magical thing in functions, as well as a convenient way of storing "references" (in C++ terminology) to potentially huge inout expressions, not to mention returning an inout from a function, effectively spreading the getter-setter awesomeness to everything else besides properties and subscripts.</div><div class=""><br class=""></div><div class="">As for variadic parameters: currently they are what I call a "dead end feature", meaning that there is no way to propagate them further and abstract them away, because you can't "unpack" a sequence into a variadic parameter (the way you can in Python with the prefix `*`), so my answer to that would also be to promote it to its own Sequence protocol conforming compiler-magic structure, which would also become part of the type system and alleviate the problem.<br class=""><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 9, 2017, at 11:07 PM, David Sweeris <<a href="mailto:davesweeris@mac.com" class="">davesweeris@mac.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: DejaVuSans; font-size: 14px; 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=""><blockquote type="cite" class=""><div class=""><br class="Apple-interchange-newline">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=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><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 style="font-family: DejaVuSans; font-size: 14px; 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="">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 style="font-family: DejaVuSans; font-size: 14px; 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 style="font-family: DejaVuSans; font-size: 14px; 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="">- Dave Sweeris</div></div></blockquote></div><br class=""></div></div></body></html>