[swift-evolution] [pitch] Variadic Arguments should accept Arrays

Haravikk swift-evolution at haravikk.me
Mon Feb 27 11:59:29 CST 2017

> On 27 Feb 2017, at 17:10, Jose Cheyo Jimenez via swift-evolution <swift-evolution at swift.org> wrote:
> On Feb 26, 2017, at 9:25 AM, Tino Heth via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> I suggest to take a look at the topics "Variadics as an Attribute" and "array splatting for variadic parameters" and https://github.com/Haravikk/swift-evolution/blob/a13dc03d6a8c76b25a30710d70cbadc1eb31b3cd/proposals/nnnn-variadics-as-attribute.md <https://github.com/Haravikk/swift-evolution/blob/a13dc03d6a8c76b25a30710d70cbadc1eb31b3cd/proposals/nnnn-variadics-as-attribute.md>.
>> This is basically the other way round (arrays would accept variadic arguments), but it has the same effect — and more:
>> You get rid of the odd "…" type, and it's also possible to use this with types besides array (set, iterator….)
> 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. 

Part of the aim is to avoid less easily discovered custom syntax; the point of the proposal is that there's no need for a special syntax just to support variadics as attributes already exist, plus they're more descriptive about what they do and easy to look-up.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170227/aa98b8ca/attachment.html>

More information about the swift-evolution mailing list