go/build: allow Import to ignore build constraints #15396
Milestone
Comments
|
why not just programmatically add all go1.x tags to
Context.BuildTags (or even Context.ReleaseTags)?
Ignoring all tags might not be what you want if you
just want to select files for future Go versions.
|
|
Adding all go1.x tags isn't sufficient because then you will reject current versions: I don't want to select for just a specific future version, but rather all possible versions from now into the future. AFAICT, the only way to achieve that with the current API would be to repeatedly invoke |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's no way at the moment to use
ImportorImportDirto select all the files in package ignoring build constraints. There is thePackage.IgnoredGoFilesfield, but that does not extend to finding the dependencies of the ignored files, and so requires extra parsing steps.One use case for this is in situations like App Engine: we want to select all the source files for an app, but not exclude source file that would be needed to compile a package in other/future versions of Go. So, we want to select files ignoring any go1.x tags.
/cc @dsymonds @adg
The text was updated successfully, but these errors were encountered: