<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div><br>On Feb 26, 2017, at 9:25 AM, Tino Heth via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div class="">I suggest to take a look at the topics "<span style="color: rgba(0, 0, 0, 0.85098); font-family: 'Helvetica Neue';" class="">Variadics as an Attribute" and "</span><font color="rgba(0, 0, 0, 0.85098)" face="Helvetica Neue" class="">array splatting for variadic parameters" and </font><a href="https://github.com/Haravikk/swift-evolution/blob/a13dc03d6a8c76b25a30710d70cbadc1eb31b3cd/proposals/nnnn-variadics-as-attribute.md" class="">https://github.com/Haravikk/swift-evolution/blob/a13dc03d6a8c76b25a30710d70cbadc1eb31b3cd/proposals/nnnn-variadics-as-attribute.md</a>.</div><div class=""><br class=""></div><div class="">This is basically the other way round (arrays would accept variadic arguments), but it has the same effect — and more:</div><div class="">You get rid of the odd "…" type, and it's also possible to use this with types besides array (set, iterator….)</div></div></blockquote><div>I agree with getting rid of the Type... because we could use ... in slicing (see String manifesto). Why must it be an attribute and not just "*" ? The advantage I see is that this will play great in also deconstructing collection like things like Array, Slice and Tuple. This is already familiar to python and ruby users. </div><div><br></div><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>