@@ -147,7 +147,7 @@ flowchart TD
147
147
148
148
### Relating an opaque type to another type
149
149
150
- There is one central place where an opaqe type gets its hidden type constrained,
150
+ There is one central place where an opaque type gets its hidden type constrained,
151
151
and that is the ` handle_opaque_type ` function.
152
152
Amusingly it takes two types, so you can pass any two types,
153
153
but one of them should be an opaque type.
@@ -216,15 +216,15 @@ and then handle it correctly.
216
216
The MIR borrow checker relates things via ` nll_relate ` and only cares about regions.
217
217
Any type relation will trigger the binding of hidden types,
218
218
so the borrow checker is doing the same thing as the type checker,
219
- but ignores obivously dead code (e.g. after a panic).
219
+ but ignores obviously dead code (e.g. after a panic).
220
220
The borrow checker is also the source of truth when it comes to hidden types,
221
221
as it is the only one who can properly figure out what lifetimes on the hidden type correspond
222
222
to which lifetimes on the opaque type declaration.
223
223
224
224
## Backwards compatibility hacks
225
225
226
226
` impl Trait ` in return position has various quirks that were not part
227
- of any RFCs and are likely accidental stabilizations .
227
+ of any RFCs and are likely accidental stabilization .
228
228
To support these,
229
229
the ` replace_opaque_types_with_inference_vars ` is being used to reintroduce the previous behaviour.
230
230
0 commit comments