# Another attempt at passing arrays as varargs (with implementation)

**URL:** <https://forums.swift.org/t/another-attempt-at-passing-arrays-as-varargs-with-implementation/26718>\
**Category:** Pitches\
**Created:** [July 8, 2019, 2:54pm UTC](https://forums.swift.org/t/another-attempt-at-passing-arrays-as-varargs-with-implementation/26718 "2019-07-08T14:54:36Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![owenv](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/owenv/32/6137_2.png) [@owenv](https://forums.swift.org/u/owenv)\
**Post date:** [July 8, 2019, 11:01pm UTC](https://forums.swift.org/t/another-attempt-at-passing-arrays-as-varargs-with-implementation/26718/29 "2019-07-08T23:01:28Z")

</div>

I think `T...` is better thought of as a sugared type. Swift doesn't allow `as ?`, `as []`, or `as [:]` today, so it shouldn't allow `as ...`. It would also likely lead to very poor diagnostics in the case of typos/programmer error if we allowed omitting the base type.

---

_[View the full topic](https://forums.swift.org/t/another-attempt-at-passing-arrays-as-varargs-with-implementation/26718)._
