Toward Go 1.3
First, I apologize for bringing up something that has been brought up since the birth of Go...<p>I'm surprised at the lack of progress in generics for Go.  But more than <i>progress</i>, I'm surprised at the lack of a <i>story</i> 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 (<a href="https://code.google.com/p/go-wiki/wiki/GoVsGenerics" rel="nofollow">https://code.google.com/p/go-wiki/wiki/GoVsGenerics</a>) is tiny and feeds from this discussion (<a href="http://groups.google.com/group/golang-nuts/browse_thread/thread/3d825ac84e742598" rel="nofollow">http://groups.google.com/group/golang-nuts/browse_thread/thr...</a>).  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.<p>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.<p>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.