rust/tests/ui/issues/issue-10465.stderr

error[E0599]: no method named `foo` found for reference `&B` in the current scope
  --> $DIR/issue-10465.rs:17:15
   |
LL |             b.foo();
   |               ^^^ method not found in `&B`
   |
   = help: items from traits can only be used if the trait is in scope
help: trait `A` which provides `foo` is implemented but not in scope; perhaps you want to import it
   |
LL +         use a::A;
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0599`.
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			error[E0599]: no method named `foo` found for reference `&B` in the current scope
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-10465.rs:17:15`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| b.foo();`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			\| ^^^ method not found in `&B`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
			`= help: items from traits can only be used if the trait is in scope`
Tweak wording of "implemented trait isn't imported" suggestion 2024-02-13 23:05:23 +00:00			help: trait `A` which provides `foo` is implemented but not in scope; perhaps you want to import it
Bless tests. 2021-08-26 18:17:19 +00:00			`\|`
Tweak output for 'add line' suggestion 2023-03-18 02:18:39 +00:00			`LL + use a::A;`
Bless tests. 2021-08-26 18:17:19 +00:00			`\|`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +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`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			For more information about this error, try `rustc --explain E0599`.