-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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, types2: improve API for setting type parameter constraints in importers #52104
Comments
@findleyr What is the current status here? This issue is currently in the 1.19 milestone. Should it move to 1.20? To Backlog? Thanks. |
Let's bump to 1.20. |
This issue is currently labeled as early-in-cycle for Go 1.23. |
@findleyr Anything to be done here at this point? Let's decide and then do or close. |
Bumping to 1.24 unless you want to close this, @findleyr . |
This issue is currently labeled as early-in-cycle for Go 1.24. |
This is unlikely to get prioritized, since there are a finite number of importers and they are all working as intended. Therefore, this is an unfortunate API, but we probably won't improve it in the near future. Keeping this open, but moving to the backlog. |
As we saw in #51219, the fact that SetConstraint eagerly computes the constraint type set makes the API awkward to use for importers.
We should investigate if this API restriction can be removed or improved.
CC @griesemer
The text was updated successfully, but these errors were encountered: