<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 dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">Actually, if you do a lot of graphics programming like I do, the memory layout is very, <i class="">very</i> important. Swift may not care about layout, but many APIs that it interacts with do. <br class=""><br class=""></div></div></div></div></blockquote><div><br class=""></div><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><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">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 class=""></div><div class=""><br class=""></div></div></div></div>
</blockquote></div><br class=""><div class="">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 class=""><br class=""></div><div class="">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><div class=""><br class=""></div><div class="">- Karl</div></body></html>