@@ -147,7 +147,7 @@ flowchart TD
147147
148148### Relating an opaque type to another type
149149
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,
151151and that is the ` handle_opaque_type ` function.
152152Amusingly it takes two types, so you can pass any two types,
153153but one of them should be an opaque type.
@@ -216,15 +216,15 @@ and then handle it correctly.
216216The MIR borrow checker relates things via ` nll_relate ` and only cares about regions.
217217Any type relation will trigger the binding of hidden types,
218218so 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).
220220The borrow checker is also the source of truth when it comes to hidden types,
221221as it is the only one who can properly figure out what lifetimes on the hidden type correspond
222222to which lifetimes on the opaque type declaration.
223223
224224## Backwards compatibility hacks
225225
226226` 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 .
228228To support these,
229229the ` replace_opaque_types_with_inference_vars ` is being used to reintroduce the previous behaviour.
230230
0 commit comments