rust/tests/ui/closures/closure-expected.stderr

error[E0277]: expected a `FnOnce()` closure, found `{integer}`
  --> $DIR/closure-expected.rs:3:23
   |
LL |     let y = x.or_else(4);
   |               ------- ^ expected an `FnOnce()` closure, found `{integer}`
   |               |
   |               required by a bound introduced by this call
   |
   = help: the trait `FnOnce<()>` is not implemented for `{integer}`
   = note: wrap the `{integer}` in a closure with no arguments: `|| { /* code */ }`
note: required by a bound in `Option::<T>::or_else`
  --> $SRC_DIR/core/src/option.rs:LL:COL

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
Pretty print Fn traits in rustc_on_unimplemented 2023-10-04 20:50:00 -05:00			error[E0277]: expected a `FnOnce()` closure, found `{integer}`
When possible point at argument causing item obligation failure 2019-09-15 23:58:20 -05:00			`--> $DIR/closure-expected.rs:3:23`
When closure with no arguments was expected, suggest wrapping 2018-08-12 14:21:53 -05:00			`\|`
			`LL \| let y = x.or_else(4);`
Pretty print Fn traits in rustc_on_unimplemented 2023-10-04 20:50:00 -05:00			\| ------- ^ expected an `FnOnce()` closure, found `{integer}`
Point at call span that introduced obligation for the arg 2021-09-07 06:30:53 -05:00			`\| \|`
			`\| required by a bound introduced by this call`
When closure with no arguments was expected, suggest wrapping 2018-08-12 14:21:53 -05: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 02:40:56 -05:00			= help: the trait `FnOnce<()>` is not implemented for `{integer}`
Add missing backticks in diagnostics note 2020-07-23 07:52:48 -05:00			= note: wrap the `{integer}` in a closure with no arguments: `\|\| { /* code */ }`
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 18:04:09 -05:00			note: required by a bound in `Option::<T>::or_else`
			`--> $SRC_DIR/core/src/option.rs:LL:COL`
When closure with no arguments was expected, suggest wrapping 2018-08-12 14:21:53 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
When closure with no arguments was expected, suggest wrapping 2018-08-12 14:21:53 -05:00
			For more information about this error, try `rustc --explain E0277`.