Re:Should Go 2.0 support generics?
by GauntletWizard on Sunday July 23, 2017 @03:07AM
(#14831201)
Go already allows you to rename imports. It's already used in the example provided, actually; the first token is the aliased name of the package.
I.e.
import intlist "container/list" {Value: int}
import stringlist "container/list" {Value: string}Thanks. I didn't realize that the second token was a user-specified name.
So, this basically would boil down to something like C++ templates, with he extra requirement that templates must be instantiated explicitly.
Even that would, IMO, not be enough, as this seems (from what I infer the semantics to be) to make it impossible for writers of such a generic library to build on another generic library.
That can be fixed by allowing such a programmer to write:
but that, IMO, would be way too cumbersome. That package declaration would have to mention all types in all generic packages that get imported.