Yup, it's a common misconception that Go language designers are anti-generics. They wanted to include generics, the reason they were left out is that there was

Yup, it's a common misconception that Go language designers are anti-generics. They wanted to include generics, the reason they were left out is that there was no clear way to include them without significant downsides: > The generic dilemma is this: do you want slow programmers, slow compilers and bloated binaries, or slow execution times? > I would be happy to learn about implementations that somehow manage to avoid all three of these bad outcomes, especially if there were good written descriptions (papers, blog posts, etc.) about what was hard and why it's a good approach. I'd also be interested to see good written descriptions of trying one of those approaches and what went wrong (or right). - Russ Cox (2009): https://research.swtch.com/generic https://research.swtch.com/generic