rust/tests/ui/trait-bounds/trait-selection-overflow-prevention-72839.stderr

error[E0425]: cannot find value `missing_var` in this scope
  --> $DIR/trait-selection-overflow-prevention-72839.rs:19:8
   |
LL |     if missing_var % 8 == 0 {}
   |        ^^^^^^^^^^^ not found in this scope

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0425`.
Don't create impl candidates when obligation contains errors Fixes #72839 In PR #72621, trait selection was modified to no longer bail out early when an error type was encountered. This allowed us treat `ty::Error` as `Sized`, causing us to avoid emitting a spurious "not sized" error after a type error had already occured. However, this means that we may now try to match an impl candidate against the error type. Since the error type will unify with almost anything, this can cause us to infinitely recurse (eventually triggering an overflow) when trying to verify certain `where` clauses. This commit causes us to skip generating any impl candidates when an error type is involved. 2020-06-04 19:32:09 -04:00			error[E0425]: cannot find value `missing_var` in this scope
Rehome tests/ui/issues/ tests [3/?] 2025-07-13 16:25:27 -04:00			`--> $DIR/trait-selection-overflow-prevention-72839.rs:19:8`
Don't create impl candidates when obligation contains errors Fixes #72839 In PR #72621, trait selection was modified to no longer bail out early when an error type was encountered. This allowed us treat `ty::Error` as `Sized`, causing us to avoid emitting a spurious "not sized" error after a type error had already occured. However, this means that we may now try to match an impl candidate against the error type. Since the error type will unify with almost anything, this can cause us to infinitely recurse (eventually triggering an overflow) when trying to verify certain `where` clauses. This commit causes us to skip generating any impl candidates when an error type is involved. 2020-06-04 19:32:09 -04:00			`\|`
			`LL \| if missing_var % 8 == 0 {}`
			`\| ^^^^^^^^^^^ not found in this scope`

Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Don't create impl candidates when obligation contains errors Fixes #72839 In PR #72621, trait selection was modified to no longer bail out early when an error type was encountered. This allowed us treat `ty::Error` as `Sized`, causing us to avoid emitting a spurious "not sized" error after a type error had already occured. However, this means that we may now try to match an impl candidate against the error type. Since the error type will unify with almost anything, this can cause us to infinitely recurse (eventually triggering an overflow) when trying to verify certain `where` clauses. This commit causes us to skip generating any impl candidates when an error type is involved. 2020-06-04 19:32:09 -04:00
			For more information about this error, try `rustc --explain E0425`.