Skip to content

Commit a2404ba

Browse files
felix91grmark-i-m
authored andcommitted
Fix typo (rust-lang#238)
"is is" ~> "it is"
1 parent ade4a4e commit a2404ba

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/traits/lowering-to-logic.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ so by applying the rules recursively:
5050

5151
- `Clone(Vec<Vec<usize>>)` is provable if:
5252
- `Clone(Vec<usize>)` is provable if:
53-
- `Clone(usize)` is provable. (Which is is, so we're all good.)
53+
- `Clone(usize)` is provable. (Which it is, so we're all good.)
5454

5555
But now suppose we tried to prove that `Clone(Vec<Bar>)`. This would
5656
fail (after all, I didn't give an impl of `Clone` for `Bar`):
@@ -130,8 +130,8 @@ Ok, so far so good. Let's move on to type-checking a more complex function.
130130
In the last section, we used standard Prolog horn-clauses (augmented with Rust's
131131
notion of type equality) to type-check some simple Rust functions. But that only
132132
works when we are type-checking non-generic functions. If we want to type-check
133-
a generic function, it turns out we need a stronger notion of goal than Prolog
134-
can be provide. To see what I'm talking about, let's revamp our previous
133+
a generic function, it turns out we need a stronger notion of goal than what Prolog
134+
can provide. To see what I'm talking about, let's revamp our previous
135135
example to make `foo` generic:
136136

137137
```rust,ignore

0 commit comments

Comments
 (0)