<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><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class=""><blockquote type="cite" class="">foo(["a", "b", "c"] as String...) <br class=""></blockquote><br class="">I like this<br class=""></blockquote><br class="">+1<br class=""></div></div></blockquote></div><br class=""><div class="">I really don't get this:</div><div class="">We have methods like NSLayoutConstraint.activate(_ constraints: [NSLayoutConstraint]), which works with an array, declares its parameter to be array and is called with an array. Quite simple.</div><div class=""><br class=""></div><div class="">On the other hand, we have functions which work with an array, but are declared with <i class="">Type…</i>, and are called with a comma-separated list of elements — and we should add an option to call this function (which works on array!) with an array that is decorated with a strange cast?</div><div class="">That looks extremely awkward to me.</div><div class=""><br class=""></div><div class="">Can I declare a variable like</div><div class="">var list: String… = "a"</div><div class="">?</div><div class="">Imho it's better to get rid of these odd types completely.</div></body></html>