They have sort.SliceStable for this I think, it's not much more verbose and is arguably clearer and more flexible as you can define exactly how the keys are com

They have sort.SliceStable for this I think, it's not much more verbose and is arguably clearer and more flexible as you can define exactly how the keys are compared (for example perhaps you want to downcase names before compare). Compare the old way to do a multi-key sort: https://play.golang.org/p/NJTVoeQkMt https://play.golang.org/p/NJTVoeQkMt With the new way: https://play.golang.org/p/6ReQxHT1lR https://play.golang.org/p/6ReQxHT1lR it's a lot simpler and clearer and doesn't require a special slice type (as it did before), but lets you sort on multiple keys if you need to. Presumably sort.SliceStable is a bit slower and that's why they have a separate sort.Slice. Note though that the old way using slice types does let you do something neater at the point of use at the cost of more setup: OrderedBy(language, increasingLines, user).Sort(changes) which in some ways is more similar to what you desired? Seeing this sort of hack added does make me think containers are the one big weak point in Go at present, they are a bit ugly, and special cases abound (append,delete,range,sort) - maybe in Go2 they could have something neater, more generic and more extensible. My hopes for Go 2 as a really uninformed language noob are a tidy up of the stdlib, variants and more elegant ways to manipulate containers (I won't say generics!), I would love to see things like magic comments and struct tags disappear too but that'll never happen. I'm pretty happy with the language otherwise, and would actually like to see Go get smaller and simpler over time.