Toward Go 1.3
First, I apologize for bringing up something that has been brought up since the birth of Go...I'm surprised at the lack of progress in generics for Go.  But more than progress, I'm surprised at the lack of a story about generics in Go.  Yes, the FAQ waves its hands at complexity, but the lack of discussion and/or proposals puzzle me.  The wiki page about it (https://code.google.com/p/go-wiki/wiki/GoVsGenerics) is tiny and feeds from this discussion (http://groups.google.com/group/golang-nuts/browse_thread/thr...).  I would be much more interested in Go were there some evidence for the intent to implement generics.  A related concern is that adding generics will have a significant affect on libraries and existing code, so adding generics will become harder the longer Go waits.I would be very happy to have the Go team say: we're going to focus on adding generics to Go in 2.0 and will be considering how to get there sooner than later; that said, we don't know when 2.0 will be released, but building in generics will drive 2.0.Note: I understand the workarounds, but they're either hacky or have terrible performance.  And I also understand that users of Go say that they don't miss generics, but I'm just not comfortable believing that.