From d41c6b64990428ddf94e96d508ddb85c9ee31bf3 Mon Sep 17 00:00:00 2001 From: Caleb Robson <94545082+Spartan2909@users.noreply.github.com> Date: Tue, 13 Jun 2023 21:42:21 +0100 Subject: [PATCH 1/3] Fix typo --- src/traits/resolution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/traits/resolution.md b/src/traits/resolution.md index 639ebbdec..991148ca6 100644 --- a/src/traits/resolution.md +++ b/src/traits/resolution.md @@ -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 need only to figure out which candidate applies, we do not care about nested obligations, 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 From 452912901f538c860d9e64b9ef4a61cf7320dbbe Mon Sep 17 00:00:00 2001 From: Caleb Robson <94545082+Spartan2909@users.noreply.github.com> Date: Tue, 13 Jun 2023 21:43:26 +0100 Subject: [PATCH 2/3] Fix typo in typo fix --- src/traits/resolution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/traits/resolution.md b/src/traits/resolution.md index 991148ca6..d2854ec08 100644 --- a/src/traits/resolution.md +++ b/src/traits/resolution.md @@ -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 need 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, 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 From 6039bbcada500f29d53da4e3211af7a8e136ff4c Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Wed, 14 Jun 2023 06:33:08 +0200 Subject: [PATCH 3/3] add missing word --- src/traits/resolution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/traits/resolution.md b/src/traits/resolution.md index d2854ec08..8fd4272a8 100644 --- a/src/traits/resolution.md +++ b/src/traits/resolution.md @@ -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 need to figure out which candidate applies, we do not care about nested obligations, +we only need to figure out which candidate applies, and we do not care about nested obligations, 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