Very interesting ideas in there. Especially the thought of an upcoming Go 2 perhaps being done in such a compatible way that "Go 2" is actually "Go 1.1X"
He also hints that it would likely only be done to address major issues/concerns/changes such as:
* generics
* modules (perhaps done? time will tell)
* errors (if err != nil {}, extra type information, chaining, etc)
* context
Still to early to tell if anything I listed or he listed would be part of "Go 2" or whatever it happens to be called.
> Very interesting ideas in there. Especially the thought of an upcoming Go 2 perhaps being done in such a compatible way that "Go 2" is actually "Go 1.1X"
The person you replied to is quoting the slides that posit that generics are a consideration for Go 2.0, so your spittle laden post betrays your own bizarre hangups.
"Cue hate, give me c# 1.1 anyday"
You brought the hate. Take it when you leave. Thanks.
He also hints that it would likely only be done to address major issues/concerns/changes such as:
* generics
* modules (perhaps done? time will tell)
* errors (if err != nil {}, extra type information, chaining, etc)
* context
Still to early to tell if anything I listed or he listed would be part of "Go 2" or whatever it happens to be called.