-
Notifications
You must be signed in to change notification settings - Fork 40
Add documentation #203
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: main
Are you sure you want to change the base?
Add documentation #203
Conversation
| /// { | ||
| /// fn drink(&self) {} // <-- `ii_fn` | ||
| /// fn smell(&self) {} // not currently being checked | ||
| /// } |
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.
this example is not fully general. I think another important part is that the instantiated trait method where-clauses imply the impl method where-clauses
|
@rustbot ready |
| // Example: we are trying to prove `x` (which equals `<SomeX<?V> as Iterator>::Item`) | ||
| // is equal to some type `z`. | ||
| ( | ||
| // Normalize `x` will find alternative "spellings" that it is equivalent to. |
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.
do we use "spellings" somewhere else? 🤔 would otherwise like to avoid even more terminology here '^^
We do use "underlying type" in rustc I think. i don't remember whether we'e talked about that before, but I feel like maybe we should change prove_normalize to take an alias type and limit the candidate to only x which are aliases
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.
👍 i changed the wording
and yeah we have an issue open for that #201, i planned to get to that soon.
Cherry-picked documentation from #194