rust/tests/ui/unsized/issue-71659.next.stderr

error[E0277]: the trait bound `dyn Foo: CastTo<[i32]>` is not satisfied
  --> $DIR/issue-71659.rs:33:15
   |
LL |     let x = x.cast::<[i32]>();
   |               ^^^^ the trait `CastTo<[i32]>` is not implemented for `dyn Foo`
   |
note: required by a bound in `Cast::cast`
  --> $DIR/issue-71659.rs:22:15
   |
LL |     fn cast<T: ?Sized>(&self) -> &T
   |        ---- required by a bound in this associated function
LL |     where
LL |         Self: CastTo<T>,
   |               ^^^^^^^^^ required by this bound in `Cast::cast`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
Use smaller example for issue-71659 2020-10-17 18:13:25 -05:00			error[E0277]: the trait bound `dyn Foo: CastTo<[i32]>` is not satisfied
Add rustc_do_not_implement_via_object 2023-06-02 00:54:52 -05:00			`--> $DIR/issue-71659.rs:33:15`
Add test for issue-71659 2020-10-14 18:35:45 -05:00			`\|`
Use smaller example for issue-71659 2020-10-17 18:13:25 -05:00			`LL \| let x = x.cast::<[i32]>();`
Point at method call when it is the source of the bound error 2022-12-11 16:49:50 -06:00			\| ^^^^ the trait `CastTo<[i32]>` is not implemented for `dyn Foo`
Point at source of trait bound obligations in more places Be more thorough in using `ItemObligation` and `BindingObligation` when evaluating obligations so that we can point at trait bounds that introduced unfulfilled obligations. We no longer incorrectly point at unrelated trait bounds (`substs-ppaux.verbose.stderr`). In particular, we now point at trait bounds on method calls. We no longer point at "obvious" obligation sources (we no longer have a note pointing at `Trait` saying "required by a bound in `Trait`", like in `associated-types-no-suitable-supertrait*`). Address part of #89418. 2021-10-05 18:04:09 -05:00			`\|`
			note: required by a bound in `Cast::cast`
Add rustc_do_not_implement_via_object 2023-06-02 00:54:52 -05:00			`--> $DIR/issue-71659.rs:22:15`
Point at source of trait bound obligations in more places Be more thorough in using `ItemObligation` and `BindingObligation` when evaluating obligations so that we can point at trait bounds that introduced unfulfilled obligations. We no longer incorrectly point at unrelated trait bounds (`substs-ppaux.verbose.stderr`). In particular, we now point at trait bounds on method calls. We no longer point at "obvious" obligation sources (we no longer have a note pointing at `Trait` saying "required by a bound in `Trait`", like in `associated-types-no-suitable-supertrait*`). Address part of #89418. 2021-10-05 18:04:09 -05:00			`\|`
			`LL \| fn cast<T: ?Sized>(&self) -> &T`
Specify what 'this' actually is 2023-02-20 23:21:07 -06:00			`\| ---- required by a bound in this associated function`
Point at source of trait bound obligations in more places Be more thorough in using `ItemObligation` and `BindingObligation` when evaluating obligations so that we can point at trait bounds that introduced unfulfilled obligations. We no longer incorrectly point at unrelated trait bounds (`substs-ppaux.verbose.stderr`). In particular, we now point at trait bounds on method calls. We no longer point at "obvious" obligation sources (we no longer have a note pointing at `Trait` saying "required by a bound in `Trait`", like in `associated-types-no-suitable-supertrait*`). Address part of #89418. 2021-10-05 18:04:09 -05:00			`LL \| where`
			`LL \| Self: CastTo<T>,`
			\| ^^^^^^^^^ required by this bound in `Cast::cast`
Add test for issue-71659 2020-10-14 18:35:45 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Add test for issue-71659 2020-10-14 18:35:45 -05:00
			For more information about this error, try `rustc --explain E0277`.