4 ms·
Are the recently introduced generics part of Go 2 - or not? I thought at one point in time the team announced that Go 2 would always be a backwards compatible e
by Matthias247 4y ago
Are the recently introduced generics part of Go 2 - or not? I thought at one point in time the team announced that Go 2 would always be a backwards compatible evolution of the language, so it seems new features could happen independent of whether one labels them as Go or Go 2.
- morelisp 4y agoBoth generics and the errors.Is/errors.As interface began life as "Go 2" projects. "Go 2" is a catch-all bucket for anything that might need to be incompatible.
- metaltyphoon 4y agoRight... so there is no Go 2. It's silly for a language that prides so much on semver and how its package versioning uses it, to make "Go 2" backwards compatible.
- morelisp 4y ago"Go 2" is not backwards compatible. Features planned for "Go 2" which are backwards compatible get backported to Go 1. This is aligned with semver.