Which isn't a bad thing, necessarily.
rsc has recently blogged in much detail about the package management situation, basing his work on existing solutions. He seems to specially eye rust's cargo. The blogs have been on HN several times.
https://news.ycombinator.com/item?id=16421966 https://news.ycombinator.com/item?id=16434973
I would guess generics, when it lands, would look syntactically similar to the way channel type declarations look; you can have "chan int", so perhaps you would have "vector int". That feels the most intuitive and Go-ish to me. Channels require special syntax to work with, but with generics, I imagine you'd want to make use of interfaces.
I can see a bunch of ways of doing it—but none I could guarantee would end up in the finished product! But I do think generics land at some point. The unfortunate thing is there's a sense going around that Go doesn't have generics because the language authors somehow know better than everyone else; if anything, I think they have an abundance of caution that some other language developers have lacked.
> When asked about the biggest challenges to their own personal use of Go, users clearly conveyed that lack of dependency management and lack of generics were their two biggest issues, consistent with 2016. In 2017 we laid a foundation to be able to address these issues
> These two issues will continue to be a major focus of the project through 2018