Six years of Go
blog.golang.org
Six years of Go
1–10 of 327 posts
Re: Six years of Go
#2Congrats to the team. Go has never let me down in my work and my personal projects, it's just awesome.
Re: Six years of Go
#3... and still no generics.
Re: Six years of Go
#4... and still no generics.
Seconded
Re: Six years of Go
#5... and still no generics.
This discussion again
Re: Six years of Go
#6... and still no generics.
Will this ever end
Re: Six years of Go
#7Re: Six years of Go
#8Feel free to downvote me if you want, but I'm skeptical about Go and what caught my attention in this linked article is the picture. Pretty much what I feel about Go. Was it a (sub)conscious choice?
Re: Six years of Go
#9... and still no generics.
Actually, Ho has generics and has had them from the beginning. But they're only available for builtin types (slices, maps), not for user-defined types/functions.
Re: Six years of Go
#10... and still no generics.
It is fairly clear by now that omitting generics is not an oversight, but rather a design choice. If you disagree, it sounds like Go isn't for you. Maybe it's time to just move on and ignore it instead of beating a dead horse.
I am always confused by the push to make every language exactly the same by using the same paradigms and features. Some languages try to take a different approach. If you can't figure out how to work within that paradigm, don't use it. Your comment is akin to complaining that Haskell doesn't support an imperative style.