<div dir="ltr"><div><div>For what it’s worth, I’d be happy with just subscripts on tuples and some form of shorthand for their size. Maybe <br><br></div>(Float ... 5)<br><br></div>or something like that. That would obviate the need for an attribute too. <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 3, 2017 at 11:48 PM, Karl Wagner <span dir="ltr"><<a href="mailto:razielim@gmail.com" target="_blank">razielim@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><span class=""><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Actually, if you do a lot of graphics programming like I do, the memory layout is very, <i>very</i> important. Swift may not care about layout, but many APIs that it interacts with do. <br><br></div></div></div></div></blockquote><div><br></div></span><div>Sure; I’m well-aware of how important it can be to decide on an appropriate memory layout. I’m very much in favour of opting-in to contiguous layout for tuples.</div><span class=""><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Is @fixed_layout actually planned to be part of the language? I was under the impression it’s just a placeholder attribute. Either way, I’d appreciate not having to write Float sixteen times for a 4x4 matrix type.<br></div><div><br></div></div></div></div>
</blockquote></span></div><br><div>AFAIK @fixed_layout is a placeholder attribute. And I’m also very much in favour of a shorthand for declaring a fixed-size list.</div><div><br></div><div>I just don’t see why we need to introduce this new kind of list-like thing in order to get what we need. It makes it harder to project a coherent message about when to use which data-type.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>- Karl</div></font></span></div></blockquote></div><br></div>