This week's book giveaways are in the Jython/Python and Object-Oriented programming forums. We're giving away four copies each of Machine Learning for Business: Using Amazon SageMaker and Jupyter and Object Design Style Guide and have the authors on-line! See this thread and this one for details.
For anyone not familiar, Generics is a common discussion point for those looking at Go. So much so, there is an entry in the FAQ about it.
Generics may well be added at some point. We don't feel an urgency for them, although we understand some programmers do.
Generics are convenient but they come at a cost in complexity in the type system and run-time. We haven't yet found a design that gives value proportionate to the complexity, although we continue to think about it. Meanwhile, Go's built-in maps and slices, plus the ability to use the empty interface to construct containers (with explicit unboxing) mean in many cases it is possible to write code that does what generics would enable, if less smoothly.
The topic remains open. For a look at several previous unsuccessful attempts to design a good generics solution for Go, see this proposal.
The typical solution for handling this in Go is using interfaces. Some folks have written about it such as the post here and here.
In my personal experience I've been able to use interfaces and a small amount of copy-and-paste to work around the lack of generics.
Is there something more specific you're curious about?