rust/tests/ui/impl-trait/issues/issue-21659-show-relevant-trait-impls-3.stderr

error[E0599]: no method named `foo` found for struct `Bar` in the current scope
  --> $DIR/issue-21659-show-relevant-trait-impls-3.rs:20:8
   |
LL | struct Bar;
   | ---------- method `foo` not found for this struct
...
LL |     f1.foo(1usize);
   |        ^^^ method not found in `Bar`
   |
   = help: items from traits can only be used if the trait is implemented and in scope
note: `Foo` defines an item `foo`, perhaps you need to implement it
  --> $DIR/issue-21659-show-relevant-trait-impls-3.rs:1:1
   |
LL | trait Foo<A> {
   | ^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
Unify output of "variant not found" errors 2020-01-08 08:05:31 -08:00			error[E0599]: no method named `foo` found for struct `Bar` in the current scope
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-21659-show-relevant-trait-impls-3.rs:20:8`
Use multiline note for trait suggestion 2017-06-02 10:15:13 -07:00			`\|`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| struct Bar;`
Track implicit `Sized` obligations in type params Suggest adding a `?Sized` bound if appropriate on E0599 by inspecting the HIR Generics. (Fix #98539) 2022-07-01 16:47:26 -07:00			\| ---------- method `foo` not found for this struct
Point to ADT definition when not finding variant, method, assoc type 2017-11-15 22:18:52 -08:00			`...`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| f1.foo(1usize);`
Give method not found a primary span label 2019-09-06 12:00:07 -07:00			\| ^^^ method not found in `Bar`
Use multiline note for trait suggestion 2017-06-02 10:15:13 -07:00			`\|`
Separate suggestion in a `help` and a `note` 2017-06-03 17:06:46 -07:00			`= help: items from traits can only be used if the trait is implemented and in scope`
keep predicate order and tweak output 2020-02-24 18:55:51 -08:00			note: `Foo` defines an item `foo`, perhaps you need to implement it
			`--> $DIR/issue-21659-show-relevant-trait-impls-3.rs:1:1`
			`\|`
			`LL \| trait Foo<A> {`
			`\| ^^^^^^^^^^^^`
Use multiline note for trait suggestion 2017-06-02 10:15:13 -07:00
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in that place, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793. 2017-07-02 16:09:09 +03:00			`error: aborting due to previous error`
Use multiline note for trait suggestion 2017-06-02 10:15:13 -07:00
update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0599`.