<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="">I think that a (4 * Int) syntax or equivalent for uniform tuples and making them subscriptable would be very helpful when dealing with C APIs that export structures with arrays in them.<br class=""><div class="">
<br class="Apple-interchange-newline"><span style="color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none;" class="">Félix</span>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">Le 28 janv. 2016 à 17:46:40, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> a écrit :</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; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jan 28, 2016, at 2:40 PM, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com" class="">jtbandes@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">What is a "type-level integer expression"? The only thing I can think of is allowing numeric parameters to generics, like "Tuple<4, Int>", but I don't think that's what you're talking about.</div></div></blockquote><div class=""><br class=""></div><div class="">That's what I mean, yeah. If we allow integers as type parameters, you'd conceivably want to use integer literals and expressions in this position too.</div><div class=""><br class=""></div><div class="">-Joe</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br clear="all" class=""><div class=""><div class=""><div dir="ltr" class=""><div class="">Jacob</div></div></div></div>
<br class=""><div class="gmail_quote">On Thu, Jan 28, 2016 at 2:38 PM, Joe Groff <span dir="ltr" class=""><<a href="mailto:jgroff@apple.com" target="_blank" class="">jgroff@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br class="">
> On Jan 28, 2016, at 2:37 PM, Joe Groff <<a href="mailto:jgroff@apple.com" target="_blank" class="">jgroff@apple.com</a>> wrote:<br class="">
><br class="">
><br class="">
>> On Jan 28, 2016, at 2:36 PM, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com" target="_blank" class="">jtbandes@gmail.com</a>> wrote:<br class="">
>><br class="">
>> I like this idea, but the syntax seems dangerously close to a call site for "func *(lhs: Int, rhs: Any.Type)" (which is obviously ill-advised, but it is allowed).<br class="">
>><br class="">
>> Maybe we could take advantage of something which would be very invalid under the current grammar, namely (n T) rather than (n * T):<br class="">
>><br class="">
>> let values: (4 Int) = (1, 2, 3, 4)<br class="">
<br class="">
</span>Bare juxtaposition might be problematic if we ever do introduce type-level integer expressions, though.<br class="">
<span class=""><font color="#888888" class=""><br class="">
-Joe</font></span></blockquote></div><br class=""></div></div>
</div></blockquote></div><br class=""></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>