Here's a more idiomatic go version: http://play.golang.org/p/oH850AdLuQ http://play.golang.org/p/oH850AdLuQ what you don't realize (apart from the fact that g

Here's a more idiomatic go version: http://play.golang.org/p/oH850AdLuQ http://play.golang.org/p/oH850AdLuQ what you don't realize (apart from the fact that go doesn't terminate lines with semicolons since 2009) is that you don't need to create a copy that's typed []interface{} because []X already satisfies interface{} and you can use reflection to handle it. if a seasoned Go programmer wanted to write a somewhat generic map function they'd do something similar to this: http://play.golang.org/p/qM8sBNcdwY http://play.golang.org/p/qM8sBNcdwY It doesn't look pretty and you're right, most go programmers don't have to write code like this. It is much more common to define a common interface for something that's map-able and expect callers to implement that. examples in sort.Interface.