I&#39;m curious why Go does&#39;t implicitly convert `[]T` to `[]interface{}` when it will implicitly convert `T` to `interface{}`.  Is there something non-trivial about this conversion that I&#39;m missing?  

Example:

    func foo([]interface{}) { /* do something */ }

    func main() {
        var a []string = []string{&quot;hello&quot;, &quot;world&quot;}
        foo(a)
    }

`go build` complains 

&gt; cannot use a (type []string) as type []interface {} in function argument

And if I try to do it explicitly, same thing: `b := []interface{}(a)` complains 

&gt;cannot convert a (type []string) to type []interface {}


So every time I need to do this conversion (which seems to come up a lot), I&#39;ve been doing something like this:

    b = make([]interface{}, len(a), len(a))
    for i := range a {
        b[i] = a[i]
    }


Is there a better way to do this, or standard library functions to help with these conversions?  It seems kind of silly to write 4 extra lines of code every time I want to call a function that can take a list of e.g. ints or strings.

All Go Interface Solutions on Gang of Coders

Total of 1 Go Interface Solutions

Type converting slices of interfaces