Well, I don't think the feedback of people that don't use (or, more specifically, who don't feel the pain of not having) generics is all that relevant. In my mi

Well, I don't think the feedback of people that don't use (or, more specifically, who don't feel the pain of not having) generics is all that relevant. In my mind, the trade-off is between potential runtime performance improvements via monomorphization vs the compile time cost of figuring out how to emit said code. I also think there's an important consideration in terms of community and ecosystem. There are plenty of examples elsewhere where splitting on some core aspect of a language had some long lasting damaging effects (python 2 vs 3, perl vs raku, D v1 phobos vs tango, etc). I don't necessarily anticipate that this would be the case here, but it'd be unfortunate if the community split into different go flavors based on similar-but-incompatible ways of doing similar types of tasks.