Should Go 2.0 support generics?
&gt; My point is that if Go is not going to have a story for templated types, then we need to own it, just like Haskell programmers own their decisions.<p>&gt; This isn’t simply a case of saying “nope, sorry, no generics for Go 2.0, maybe in another 5 years”, but a more fundamental statement that they are not something that will be implemented in Go because we believe there is a better way to solve the underlying problem.<p>ffs. tldr; yes. Add generics.<p>Come on, the feedback from the community has been overwhelming.<p>If we were going to &#x27;own&#x27; not having generics, we wouldn&#x27;t be having this conversation.<p>There&#x27;s a disconnect here, clearly, between the community and what the community wants, and what the language makers and designers want.<p>I think what Dave is advocating here is basically the &#x27;status quo&#x27; from golang 1.0 (ie. we&#x27;ll never have generics).<p>That hasn&#x27;t worked.<p>Lets not do it again.