Closed kevinburkesegment closed 2 years ago
Are we dropping compatibility with 1.16 if we remove +build?
Yes, I think so, but note the go formatter is doing this automatically. So we either need to use 1.16/1.17 to generate these files always, or upgrade.
IMO if you care enough about perf to use this library you should be given carrots to upgrade, or interested in upgrading.
The segmentio/encoding package depends on this one, users may have indirect dependencies on segmentio/asm, that would break compilation of their programs then.
I'm not against making the change but I think we need to carefully vet the impact, and take proactive steps to mitigate it, for example:
For what it's worth, I think supporting the last two Go versions is a common practice since it matches the support policy of Go itself.
Ok - I've done everything on the list here: https://github.com/segmentio/asm/pull/76#issuecomment-1105908240
Also regenerate all of the stubs, we don't need "+build" anymore because both Go 1.17 and 1.18 use "go:build" for build tags.