-
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
cmd/api: API checker doesn't seem to handle Alias uses correctly #65437
Comments
I think this might not be a bug in the API checker. I think it might actually be a problem with whether we can move types. Suppose package |
See https://go.dev/doc/go1compat , Compatibility is at the source level. From the above blog about compatibility, I can't tell if fmt.Printf("%v\n", reflect.ValueOf(a.T{}).Type()) output a.T backward compatibility is guaranteed to not change it? |
@randall77 I seems to me that explicit Alias type nodes should allow us to fix this: that is, if That said, per the original alias proposal, we already have issue with reflect (link). |
Moving to 1.24. Not urgent. |
Didn't get to this. For 1.25. |
Background: API check failure in https://go.dev/cl/559435.
The text was updated successfully, but these errors were encountered: