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

error[E0277]: expected a `FnMut(_, char)` closure, found `()`
  --> $DIR/issue-23966.rs:2:32
   |
LL |     "".chars().fold(|_, _| (), ());
   |                ----            ^^ expected an `FnMut(_, char)` closure, found `()`
   |                |
   |                required by a bound introduced by this call
   |
   = help: the trait `FnMut<(_, char)>` is not implemented for `()`
note: required by a bound in `fold`
  --> $SRC_DIR/core/src/iter/traits/iterator.rs:LL:COL

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
Pretty print Fn traits in rustc_on_unimplemented 2023-10-05 01:50:00 +00:00			error[E0277]: expected a `FnMut(_, char)` closure, found `()`
When possible point at argument causing item obligation failure 2019-09-16 04:58:20 +00:00			`--> $DIR/issue-23966.rs:2:32`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
			`LL \| "".chars().fold(\|_, _\| (), ());`
Pretty print Fn traits in rustc_on_unimplemented 2023-10-05 01:50:00 +00:00			\| ---- ^^ expected an `FnMut(_, char)` closure, found `()`
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`
When closure with no arguments was expected, suggest wrapping 2018-08-12 19:21:53 +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			= help: the trait `FnMut<(_, char)>` is not implemented for `()`
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 `fold`
			`--> $SRC_DIR/core/src/iter/traits/iterator.rs:LL:COL`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			`error: aborting due to previous error`

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