-
Notifications
You must be signed in to change notification settings - Fork 12.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
Associated types are used as inputs for multidispatch #18437
Comments
This is important for 1.0 primarily because we want to prevent people from doing things like implementing |
This is fixed now. |
For posterity: it was fixed during the rewrite of associated types to not use synthetic type parameters. |
lnicola
pushed a commit
to lnicola/rust
that referenced
this issue
Nov 4, 2024
Publish test-fixture => ra_ap_test_fixture
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently associated types are expanded into synthetic type parameters that also lie in the same 'space' as the normal trait type parameters. This means they will be treated like inputs rather than outputs. We should fix this.
The text was updated successfully, but these errors were encountered: