Go uses structural typing which feels like duck typing but it's actually checked at compile time. That's the reason why the Go community feels generics are not

Go uses structural typing which feels like duck typing but it's actually checked at compile time. That's the reason why the Go community feels generics are not the top priority (euphemism.) Only in very specific cases (implementing data structures, for example) you can feel the need for generics. Maybe also in serialization, although that's really normal to pass a generic container (object, void *, interface{}) and use introspection.