<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=""><div><br class=""><blockquote type="cite" class=""><div class=""><p 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-stroke-width: 0px; margin: 0px 0px 1.2em !important;" class="">I think that tuples should remain what they are now. Static-length vectors should be types on their own and interact with tuples, with structs and with<span class="Apple-converted-space"> </span><code style="font-size: 0.85em; font-family: Consolas, Inconsolata, Courier, monospace; margin: 0px 0.15em; padding: 0px 0.3em; white-space: pre-wrap; border: 1px solid rgb(234, 234, 234); background-color: rgb(248, 248, 248); border-top-left-radius: 3px; border-top-right-radius: 3px; border-bottom-right-radius: 3px; border-bottom-left-radius: 3px; display: inline;" class="">Array<…></code><span class="Apple-converted-space"> </span>in the same way.</p></div></blockquote>I strongly agree: Fixed-size vectors are a well known and simple concept that shouldn't be conflated with tuples.</div><div><br class=""></div><div>Afair there was a time when Swift had no set-type, and I think we are lucky that it was added, instead of forcing us to use other collections instead.</div><div>Mixing array and tuple feels like having a switch for array to behave like a set...</div></body></html>