| ▲ | pdimitar a day ago | ||||||||||||||||||||||||||||||||||
RE: Golang v2, they clearly said they will not do it and will double down on backwards compatibility with exceptions powered by env vars and/or CLI switches. | |||||||||||||||||||||||||||||||||||
| ▲ | 9rx a day ago | parent | next [-] | ||||||||||||||||||||||||||||||||||
Technically, Go v2 signified the transition away from Google control to the project being directed by the community. That happened several years ago. Go v2 is already here and has been for a long time. The stdlib is also at v2 now (e.g. math/rand/v2). You must mean the language? They said that a language v2 (go2) is probably unnecessary – that any future additions could be added without breaking the existing language. I don't expect simple tagged unions would need to break anything. A v2 (or even v3, perhaps) stdlib would be necessary to take advantage, like the parent suggests, but that has never been ruled out and is already the status quo. | |||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||
| ▲ | packetlost a day ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||
I'm fully aware of that. | |||||||||||||||||||||||||||||||||||