I for one like not having things rushed in which then cannot be changed later on.
Does this mean Go is perfect? Not at all.
It just means I'd rather have generics late than fundamentally broken.
Does this mean Go is perfect? Not at all.
It just means I'd rather have generics late than fundamentally broken.
Now if that would have been part of Go 1.0....
Go is about compatibility, being able to control your code base and being confident about results and I'd really prefer them to take their time thinking through a non-critical feature rather then rushing it and exploring all sorts of unexpected side effects down the road.
Go actively decided against generics in the beginning to make a small and simple language. We will lose that now.