Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go: build tags for beta and RC builds clarification #26458
I would like to get some clarification about how the build tags for Go versions work.
For example, we have now Go 1.11 Beta 1, which I would expect to use the
However, currently Go 1.11 Beta 1 seems to use
Have I missed something from the way build tags should work? Or if this is undocumented/unwritten can we please get some more official information on it?
I've always understood the reasoning to be the API versioning, i.e. what you can find in files like
I think you're right that the documentation is a bit lacking, though. From https://tip.golang.org/pkg/go/build/#hdr-Build_Constraints:
I think we should explicitly say something like "including 1.11 betas and RCs". Although if this is hidden in
Thanks for the reply.
This is more about documenting the behavior than providing individual build tags for each beta/RC release.
It could be possible to want to prevent a point release, e.g.
That's why I think it's useful to have the documentation cleared with regards to what a