From ddb3d38965d9ef1ca47cb1c293d23623e0f95efa Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Sun, 17 Jul 2022 23:10:35 +0200 Subject: [PATCH] obey line length limit (part 2) --- src/opaque-types-type-alias-impl-trait-inference.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/opaque-types-type-alias-impl-trait-inference.md b/src/opaque-types-type-alias-impl-trait-inference.md index 4e86d8c9..a3c699e3 100644 --- a/src/opaque-types-type-alias-impl-trait-inference.md +++ b/src/opaque-types-type-alias-impl-trait-inference.md @@ -188,7 +188,13 @@ The registered hidden types are stored into the `QueryResponse` struct in the `o When the `QueryResponse` is instantiated into the surrounding infcx in `query_response_substitution_guess`, we convert each hidden type constraint by invoking `handle_opaque_type` (as above). -There is one bit of "weirdness". The instantiated opaque types are stored in a *map*, and we have to pick one opaque type to use as the key of that map. We use the one that is considered "expected". But really both of the opaque types may have defining uses. When the query result is instantiated, that will be re-evaluated from the context that is using the query. +There is one bit of "weirdness". +The instantiated opaque types are stored in a *map*, +and we have to pick one opaque type to use as the key of that map. +We use the one that is considered "expected". +But really both of the opaque types may have defining uses. +When the query result is instantiated, +that will be re-evaluated from the context that is using the query. ### Within the MIR borrow checker