[orph4nus]

I think they are still open to it, in a very sceptical way. Basically they are asking [1] the public/users for papers/documents/articles/blogs, describing the use cases of generics in Golang. How would they use it? Why is it required (as in can you not do it easily/better without generics)? Stuff like that. They basically aren't convinced that generics is something they need/want in Go, but if the users can convince them, they will still go for it in the future of Go.

[1]: https://blog.golang.org/toward-go

   "I'm focusing today on possible major changes, such as 
   additional support for error handling, or introducing 
   immutable or read-only values,
   or adding some form of generics,
   or other important topics not yet suggested.

   We can do only a few of those major changes.
   We will have to choose carefully."

[GenericsMotors]

I find it interesting that they're asking the community what the use cases for generics are, when internally Go does support generics for its built-in collection types...hmmm I wonder why?!

Maybe because it provides compile-time type safety and reduces the amount of boilerplate that would otherwise be required. Yet they can't see the usefulness outside of this single case?

Seems disingenuous to me.

[pjmlp]

Basically it allows for any Gofer on HN and similar forums to defend the idea "they are working on it" without any actual visible action.