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-05 01:50:00 +00:00			error[E0277]: expected a `FnOnce()` closure, found `{integer}`
When possible point at argument causing item obligation failure 2019-09-16 04:58:20 +00:00			`--> $DIR/closure-expected.rs:3:23`
When closure with no arguments was expected, suggest wrapping 2018-08-12 19:21:53 +00:00			`\|`
			`LL \| let y = x.or_else(4);`
Pretty print Fn traits in rustc_on_unimplemented 2023-10-05 01:50:00 +00:00			\| ------- ^ expected an `FnOnce()` closure, found `{integer}`
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			`\|`
Use parenthetical notation for `Fn` traits Always use the `Fn(T) -> R` format when printing closure traits instead of `Fn<(T,), Output = R>`. Fix #67100: ``` error[E0277]: expected a `Fn()` closure, found `F` --> file.rs:6:13 \| 6 \| call_fn(f) \| ------- ^ expected an `Fn()` closure, found `F` \| \| \| required by a bound introduced by this call \| = note: wrap the `F` in a closure with no arguments: `\|\| { /* code */ }` note: required by a bound in `call_fn` --> file.rs:1:15 \| 1 \| fn call_fn<F: Fn() -> ()>(f: &F) { \| ^^^^^^^^^^ required by this bound in `call_fn` help: consider further restricting this bound \| 5 \| fn call_any<F: std::any::Any + Fn()>(f: &F) { \| ++++++ ``` 2024-05-29 21:42:40 +00:00			= help: the trait `FnOnce()` is not implemented for `{integer}`
Add missing backticks in diagnostics note 2020-07-23 12:52:48 +00: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 23:04:09 +00: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 19:21:53 +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`
When closure with no arguments was expected, suggest wrapping 2018-08-12 19:21:53 +00:00
			For more information about this error, try `rustc --explain E0277`.