rust/tests/ui/suggestions/into-str.stderr

error[E0277]: the trait bound `&str: From<String>` is not satisfied
  --> $DIR/into-str.rs:4:9
   |
LL |     foo(String::new());
   |     --- ^^^^^^^^^^^^^ the trait `From<String>` is not implemented for `&str`
   |     |
   |     required by a bound introduced by this call
   |
   = note: to coerce a `String` into a `&str`, use `&*` as a prefix
   = help: the following other types implement trait `From<T>`:
             <String as From<&String>>
             <String as From<&mut str>>
             <String as From<&str>>
             <String as From<Box<str>>>
             <String as From<Cow<'a, str>>>
             <String as From<char>>
   = note: required for `String` to implement `Into<&str>`
note: required by a bound in `foo`
  --> $DIR/into-str.rs:1:31
   |
LL | fn foo<'a, T>(_t: T) where T: Into<&'a str> {}
   |                               ^^^^^^^^^^^^^ required by this bound in `foo`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
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[E0277]: the trait bound `&str: From<String>` is not satisfied
fix(rustc_typeck): report function argument errors on matching type Fixes #90101 2021-10-22 20:49:12 +00:00			`--> $DIR/into-str.rs:4:9`
Add suggestion to use `&*var` when `&str: From<String>` is expected 2019-03-18 05:42:51 +00:00			`\|`
			`LL \| foo(String::new());`
fix(rustc_typeck): report function argument errors on matching type Fixes #90101 2021-10-22 20:49:12 +00:00			\| --- ^^^^^^^^^^^^^ the trait `From<String>` is not implemented for `&str`
			`\| \|`
			`\| required by a bound introduced by this call`
Add suggestion to use `&*var` when `&str: From<String>` is expected 2019-03-18 05:42:51 +00:00			`\|`
fix rustc_on_implemented `_Self` paths 2021-03-12 10:48:05 +00:00			= note: to coerce a `String` into a `&str`, use `&*` as a prefix
Refer to the TraitRef::identity in the message to be clearer 2022-03-27 02:02:07 +00:00			= help: the following other types implement trait `From<T>`:
further update `fuzzy_match_tys` 2022-02-11 15:12:22 +00:00			`<String as From<&String>>`
			`<String as From<&mut str>>`
			`<String as From<&str>>`
			`<String as From<Box<str>>>`
Fix list length 2022-03-26 23:14:47 +00:00			`<String as From<Cow<'a, str>>>`
			`<String as From<char>>`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 20:31:37 +00:00			= note: required for `String` to implement `Into<&str>`
Use note to point at bound introducing requirement 2021-07-31 16:26:55 +00:00			note: required by a bound in `foo`
			`--> $DIR/into-str.rs:1:31`
			`\|`
			`LL \| fn foo<'a, T>(_t: T) where T: Into<&'a str> {}`
			\| ^^^^^^^^^^^^^ required by this bound in `foo`
Add suggestion to use `&*var` when `&str: From<String>` is expected 2019-03-18 05:42:51 +00:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0277`.