-
Notifications
You must be signed in to change notification settings - Fork 1
document trait bounds and candidate preference behavior #7
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
base: reference
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of nits and a question, but the overall structure and organization of this seems potentially reasonable.
|
🤷 idk how to make progress here, would be nice if someone could look over this again. |
| ``` | ||
|
|
||
| r[items.generics.instantiation] | ||
| When using an item its generic parameters have to get instantiated. This replaces all occurances of the parameter with either the explicitly provided argument or a new unconstrained inference variable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| When using an item its generic parameters have to get instantiated. This replaces all occurances of the parameter with either the explicitly provided argument or a new unconstrained inference variable. | |
| When using an item its generic parameters have to get instantiated. This replaces all occurances of the parameter with either the explicitly provided argument or a new inference variable. |
cc #3
documents http://github.com/rust-lang/rust/pull/120752
would be nice for somebody to quickly skim over this to detect
how to talk about X
how to talk about relating higher ranked types. "instantiating the
forof the subtype with inference variables and theforof the supertype with placeholders before relating them as normal" seems quite cumbersome. This is where using judgements/actual code is actually ncier than text.concepts which I don't know how to avoid
rigid types: a type which cannot be normalized in teh current context, whose equality is implemented by equating the type constructor and then recursively their corresponding generic arguments