What I'd like to see in Go 2.0

This isn't too bad - usually these articles include a laundry list of features to make language X into Java: exceptions, Java-like standard library so you nominally only have to do "business logic", traits, Java-style generics. You know, like PHP is doing to itself. But this article advocates for a more moderate, Go-philosophy-consistent set of changes. Except for the "range should generate references" one - "range" pre-generates values so that there's some thread-safety when looping, other choices mean a C++ style abbatoir when it comes to iteration.

I like the list and it mostly matches my pain points when I worked with Go several years in the past.

That being said: is Go 2.0, which would be backwards-incompatible with Go 1.x, even expected to come into existence, like ever?