rust/tests/ui/suggestions/issue-62843.stderr

error[E0277]: expected a `FnMut<(char,)>` closure, found `String`
  --> $DIR/issue-62843.rs:4:32
   |
LL |     println!("{:?}", line.find(pattern));
   |                           ---- ^^^^^^^ the trait `Pattern<'_>` is not implemented for `String`
   |                           |
   |                           required by a bound introduced by this call
   |
   = note: the trait bound `String: Pattern<'_>` is not satisfied
   = note: required for `String` to implement `Pattern<'_>`
note: required by a bound in `core::str::<impl str>::find`
  --> $SRC_DIR/core/src/str/mod.rs:LL:COL
help: consider borrowing here
   |
LL |     println!("{:?}", line.find(&pattern));
   |                                +

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]: expected a `FnMut<(char,)>` closure, found `String`
When possible point at argument causing item obligation failure 2019-09-16 04:58:20 +00:00			`--> $DIR/issue-62843.rs:4:32`
Add note suggesting to borrow a String argument to find 2019-07-25 17:11:03 +00:00			`\|`
			`LL \| println!("{:?}", line.find(pattern));`
Adjust messages, address some nits 2022-08-18 12:16:35 +00:00			\| ---- ^^^^^^^ the trait `Pattern<'_>` is not implemented for `String`
fix test error 2021-09-26 15:50:46 +00:00			`\| \|`
Point at call span that introduced obligation for the arg 2021-09-07 11:30:53 +00:00			`\| required by a bound introduced by this call`
Add note suggesting to borrow a String argument to find 2019-07-25 17:11:03 +00:00			`\|`
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			= note: the trait bound `String: Pattern<'_>` is not satisfied
Reword "Required because of the requirements on the impl of ..." 2022-08-15 20:31:37 +00:00			= note: required for `String` to implement `Pattern<'_>`
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 `core::str::<impl str>::find`
			`--> $SRC_DIR/core/src/str/mod.rs:LL:COL`
fix test error 2021-09-26 15:50:46 +00:00			`help: consider borrowing here`
			`\|`
			`LL \| println!("{:?}", line.find(&pattern));`
			`\| +`
Add note suggesting to borrow a String argument to find 2019-07-25 17:11:03 +00:00
			`error: aborting due to previous error`

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