-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go/types: unexport the GoVersion configuration option for Go 1.17 #46296
Comments
No proposal here either. |
This change was ported from types2, where it was needed IIRC to support |
Some features (and thus error messages) depend on the Go version. As long as we're ok with |
To clarify, I think this is a useful feature, and we should expose it eventually. But the fact that it was exposed in go/types for 1.17 was incidental. The real reason it was added was for consistency with types2 (and because it has value of course). At the time we weren't thinking about 1.17. If we think it's minor enough not to require a proposal, we can leave it in, but I certainly don't want it to be perceived as bypassing the proposal process. Since no one is clamoring for this change, unexporting the field and making a brief proposal at the start of the 1.18 cycle seems like a fine option. I feel roughly the same about #46298, though I think that change is even more minor. I defer to both of you, as members of the proposal committee, for what is OK. |
Sorry for not being clear: What I meant is that we don't need to expose this for Go1.17. We can discuss what needs to be done for Go1.18. |
Change https://golang.org/cl/323430 mentions this issue: |
Filed a proposal at #46648 to discuss this feature for 1.18. |
+pkg go/types, type Config struct, GoVersion string
The
GoVersion
field was added totypes.Config
to configure the language version being type checked.CC @griesemer
The text was updated successfully, but these errors were encountered: