I agree generic would be a serious win for Golang. However in the meantime we have this workaround/hack which alleviates some of the pain http://clipperhouse.github.io/gen/
Lisp manipulation? Do you mean linked lists, or arraylists? The only common use of linked lists I've encountered is writing custom allocators, and most programs don't need custom allocators.
Go "lists" are type dynamic -- "generics" in the most important place for generics to be.
Heterogeneous lists are not "generics."
A Go map is of the defintion map[KeyType]ValueType. A Go slice and dynamic array is similar typed. That isn't heterogeneous, it isn't of type object, and is 99% of the common use of generics.
Yeah, the native fundamental collections are generic.
I have a feeling we're talking about different things: when people speak about Go generics, they mean that the language doesn't support parametric polymorphism. Yes, some of the built-in types are special. That's not the point.
lolwhat? How exactly would list manipulations in Go be made easier because of generics?
How many of these[1] functions can I write in Go without doing a bunch of casting? Probably less than half.