rust/tests/ui/traits/vtable-res-trait-param.stderr

error[E0277]: the trait bound `{integer}: TraitA` is not satisfied
  --> $DIR/vtable-res-trait-param.rs:17:18
   |
LL |     b.gimme_an_a(y)
   |       ---------- ^ the trait `TraitA` is not implemented for `{integer}`
   |       |
   |       required by a bound introduced by this call
   |
help: this trait has no implementations, consider adding one
  --> $DIR/vtable-res-trait-param.rs:1:1
   |
LL | trait TraitA {
   | ^^^^^^^^^^^^
note: required by a bound in `TraitB::gimme_an_a`
  --> $DIR/vtable-res-trait-param.rs:6:21
   |
LL |     fn gimme_an_a<A:TraitA>(&self, a: A) -> isize;
   |                     ^^^^^^ required by this bound in `TraitB::gimme_an_a`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			error[E0277]: the trait bound `{integer}: TraitA` is not satisfied
When possible point at argument causing item obligation failure 2019-09-16 04:58:20 +00:00			`--> $DIR/vtable-res-trait-param.rs:17:18`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| b.gimme_an_a(y)`
Point at call span that introduced obligation for the arg 2021-09-07 11:30:53 +00:00			\| ---------- ^ the trait `TraitA` is not implemented for `{integer}`
			`\| \|`
			`\| required by a bound introduced by this call`
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 23:04:09 +00:00			`\|`
Point out if a local trait has no implementations 2023-09-10 03:33:07 +00:00			`help: this trait has no implementations, consider adding one`
			`--> $DIR/vtable-res-trait-param.rs:1:1`
			`\|`
			`LL \| trait TraitA {`
			`\| ^^^^^^^^^^^^`
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 23:04:09 +00:00			note: required by a bound in `TraitB::gimme_an_a`
			`--> $DIR/vtable-res-trait-param.rs:6:21`
			`\|`
			`LL \| fn gimme_an_a<A:TraitA>(&self, a: A) -> isize;`
			\| ^^^^^^ required by this bound in `TraitB::gimme_an_a`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
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`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
			For more information about this error, try `rustc --explain E0277`.