Please note that these are not all the possible build tags. Anyone can set up their own custom build tags.

What you seem to be listing here is all the (current) possible values of GOOS and GOARCH, which you can also use as build tags. Is that what you'd be interested in?

Also note that if you meant all the build tags recognized by the Go toolchain, that list is not complete either - there's also unix, test, fuzz among others.

https://github.com/dvyukov/go-fuzz (this one isn't part of the Go toolchain at the moment, but it may be in the future)

After a quick search, I found #12270, but that's not in any Go package and it's all the possible combinations, not the values separately.

I don't really think this is well-formed. Any such list is going to be out-of-date / dependent on a very specific Go version. If you want to strip a file name of _foo suffixes, I would just remove any underscores anywhere.

I don't really think this is well-formed. Any such list is going to be out-of-date / dependent on a very specific Go version.

I don't understand why a maintenance concern makes this malformed.

Perhaps it's possible to generate a go/build declaration from lists of OS and arch build tags defined elsewhere?

If you want to strip a file name of _foo suffixes, I would just remove any underscores anywhere.

From go doc go/build:

If a file's name, after stripping the extension and a possible _test suffix, matches any of the following patterns:

*_GOOS
*_GOARCH
*_GOOS_GOARCH

(example: source_windows_amd64.go) where GOOS and GOARCH represent any known operating system and architecture values respectively, then the file is considered to have an implicit build constraint requiring those terms (in addition to any explicit constraints in the file).

If I understand correctly, then foo_bar.go is a valid Go file name with no build tags in the name, and foo_bar_windows_amd64.go is a valid Go file name with OS and arch build tags in the name. If by "remove any underscores anywhere" you mean "strip a file name of _foo suffixes", then "_bar" would be stripped as well, which is incorrect.