Closed peterhellberg closed 11 months ago
I assume we want both of these supported by the library as of right now?
I think that'd be nice, yes.
to document how you would like to deal with additions to the language going forward
Honestly, I don't have an opinion, other than supporting what's reasonable. What do you suggest?
I suggest targeting the two supported versions going forward in order to allow more people to use the library but still not get stuck in supporting no longer supported versions of the language. This means that we would wait with usage of newly introduced functionality until it has landed in the previous version. (A delay of half a year or so in general)
This would imply keeping the go
module directive as 1.20
for the time being. And only bumping that if required by some new functionality supported in both (at the time) currently supported Go versions.
Well said. I agree.
The currently supported versions of Go are
1.21
and1.20
. I assume we want both of these supported by the library as of right now?(I thought it could be good to open an issue to document how you would like to deal with additions to the language going forward, such as
slices.Equal
introduced in1.21
)