about summary refs log tree commit diff
path: root/src/libstd
diff options
context:
space:
mode:
authorNiko Matsakis <niko@alum.mit.edu>2016-11-02 18:08:32 -0400
committerNiko Matsakis <niko@alum.mit.edu>2016-11-02 18:18:24 -0400
commitb4f910d9004f09620ef5b1aff5d676c1dab7d42f (patch)
treec811cc429d3c3c71c2b799f5279841671809f032 /src/libstd
parentd9bc86032d0aa20db522e04a550deb1034005784 (diff)
downloadrust-b4f910d9004f09620ef5b1aff5d676c1dab7d42f.tar.gz
rust-b4f910d9004f09620ef5b1aff5d676c1dab7d42f.zip
just use full-normalization when for the impl trait ref
This seems better because I want to avoid the situation where unresolved
inference variables make it into the environment.  On the other hand, I
am not 100% sure that this is correct. My assumption was that the WF
check should ensure that this normalization can succeed. But it occurs
to me that the WF checks may need to make use of the `specializes`
predicate themselves, and hence we may have a kind of cycle here (this
is a bigger problem with spec in any case that we need to resolve).

On the other hand, this should just cause extra errors I think, so it
seems like a safe thing to attempt. Certainly all tests pass.
Diffstat (limited to 'src/libstd')
0 files changed, 0 insertions, 0 deletions