Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix typo #1697

Merged
merged 3 commits into from
Jun 14, 2023
Merged

Fix typo #1697

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d41c6b6
Fix typo
Spartan2909 Jun 13, 2023
4529129
Fix typo in typo fix
Spartan2909 Jun 13, 2023
6039bbc
add missing word
tshepang Jun 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/traits/resolution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -247,7 +247,7 @@ In this second selection, we do not consider any where-clauses to be in scope
because we know that each resolution will resolve to a particular impl.

One interesting twist has to do with nested obligations. In general, in codegen,
we only to figure out which candidate applies, we do not care about nested obligations,
we only need to figure out which candidate applies, we do not care about nested obligations,
tshepang marked this conversation as resolved.
Show resolved Hide resolved
as these are already assumed to be true. Nonetheless, we *do* currently fulfill all of them.
That is because it can sometimes inform the results of type inference.
That is, we do not have the full substitutions in terms of the type variables
Expand Down