Skip to content

Commit a7b88b4

Browse files
committed
Edits to unresolved questions
1 parent dfc73d9 commit a7b88b4

File tree

1 file changed

+4
-9
lines changed

1 file changed

+4
-9
lines changed

text/0000-conservative-impl-trait.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -545,12 +545,7 @@ types private to a function body, for example an iterator adapter containing a c
545545

546546
> What parts of the design are still TBD?
547547

548-
- What happens if you specialize a function with an abstract return type,
549-
and differ in whether the return type implements an OIBIT or not?
550-
- It would mean that specialization choice
551-
has to flow back into typechecking.
552-
- It seems sound, but would mean that different input type combinations
553-
of such a function could cause different OIBIT behavior independent
554-
of the input type parameters themself.
555-
- Which would not necessarily be an issue, since the actual type could not
556-
be observed from the outside anyway.
548+
The precise implementation details for OIBIT transparency are a bit unclear: in
549+
general, it means that type checking may need to proceed in a particular order,
550+
since you cannot get the full type information from the signature alone (you
551+
have to typecheck the function body to determine which OIBITs apply).

0 commit comments

Comments
 (0)