rust/src/test/ui/impl-trait/issue-21659-show-relevant-trait-impls-3.stderr

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

error: aborting due to previous error

If you want more information on this error, try using "rustc --explain E0599"
Use multiline note for trait suggestion 2017-06-02 12:15:13 -05:00			error[E0599]: no method named `foo` found for type `Bar` in the current scope
			`--> $DIR/issue-21659-show-relevant-trait-impls-3.rs:30:8`
			`\|`
Point to ADT definition when not finding variant, method, assoc type 2017-11-16 00:18:52 -06:00			`23 \| struct Bar;`
			\| ----------- method `foo` not found for this
			`...`
Use multiline note for trait suggestion 2017-06-02 12:15:13 -05:00			`30 \| f1.foo(1usize);`
			`\| ^^^`
			`\|`
Separate suggestion in a `help` and a `note` 2017-06-03 19:06:46 -05:00			`= help: items from traits can only be used if the trait is implemented and in scope`
			= note: the following trait defines an item `foo`, perhaps you need to implement it:
Use multiline note for trait suggestion 2017-06-02 12:15:13 -05:00			candidate #1: `Foo`

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 08:09:09 -05:00			`error: aborting due to previous error`
Use multiline note for trait suggestion 2017-06-02 12:15:13 -05:00
Update ui tests 2018-02-19 14:40:25 -06:00			`If you want more information on this error, try using "rustc --explain E0599"`