[krakensden]

The usual pattern is to use a type that requires the thing you pass in to have methods that you use for the data structure, like sort.Interface[1]. It's faster, safer, and better than using interface{}.

As for shorthand, behold!

    type any interface{}

[1]: http://golang.org/pkg/sort/#Interface

[codeflo]

That introduces a new named type though, i.e., the "any" in your package is different from the "any" in mine, which is not what I want.

(Unless I'm mistaken here, which might very well be the case.)

[krakensden]

Check it out: http://play.golang.org/p/l9yn0PRbrd

Anyway, that's the point of go's type inference- if the object implements the necessary parts of the interface, it counts as that kind of object.