Skip to content

Commit

Permalink
remove workaround that prints error messages with TyErr
Browse files Browse the repository at this point in the history
now that normalize_to_error no longer creates these, it is unnecessary.
  • Loading branch information
Ariel Ben-Yehuda authored and arielb1 committed Apr 5, 2016
1 parent 953c3b5 commit 513d9f2
Showing 1 changed file with 1 addition and 6 deletions.
7 changes: 1 addition & 6 deletions src/librustc/traits/error_reporting.rs
Expand Up @@ -90,12 +90,7 @@ pub fn report_projection_error<'a, 'tcx>(infcx: &InferCtxt<'a, 'tcx>,
let predicate =
infcx.resolve_type_vars_if_possible(&obligation.predicate);

// The TyError created by normalize_to_error can end up being unified
// into all obligations: for example, if our obligation is something
// like `$X = <() as Foo<$X>>::Out` and () does not implement Foo<_>,
// then $X will be unified with TyError, but the error still needs to be
// reported.
if !infcx.tcx.sess.has_errors() || !predicate.references_error() {
if !predicate.references_error() {
let mut err = struct_span_err!(infcx.tcx.sess, obligation.cause.span, E0271,
"type mismatch resolving `{}`: {}",
predicate,
Expand Down

0 comments on commit 513d9f2

Please sign in to comment.