rust/tests/ui/unboxed-closures/unboxed-closures-fnmut-as-fn.stderr

error[E0277]: expected a `Fn<(isize,)>` closure, found `S`
  --> $DIR/unboxed-closures-fnmut-as-fn.rs:27:21
   |
LL |     let x = call_it(&S, 22);
   |             ------- ^^ expected an `Fn<(isize,)>` closure, found `S`
   |             |
   |             required by a bound introduced by this call
   |
   = help: the trait `Fn<(isize,)>` is not implemented for `S`
   = note: `S` implements `FnMut`, but it must implement `Fn`, which is more general
note: required by a bound in `call_it`
  --> $DIR/unboxed-closures-fnmut-as-fn.rs:22:14
   |
LL | fn call_it<F:Fn(isize)->isize>(f: &F, x: isize) -> isize {
   |              ^^^^^^^^^^^^^^^^ required by this bound in `call_it`

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 02:40:56 -05:00			error[E0277]: expected a `Fn<(isize,)>` closure, found `S`
Cleanup feature gates. 2022-01-19 09:24:49 -06:00			`--> $DIR/unboxed-closures-fnmut-as-fn.rs:27:21`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| let x = call_it(&S, 22);`
Point at call span that introduced obligation for the arg 2021-09-07 06:30:53 -05:00			\| ------- ^^ expected an `Fn<(isize,)>` closure, found `S`
			`\| \|`
			`\| required by a bound introduced by this call`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -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 `Fn<(isize,)>` is not implemented for `S`
Better suggestions for Fn trait selection errors 2022-03-23 22:57:48 -05:00			= note: `S` implements `FnMut`, but it must implement `Fn`, which is more general
Use note to point at bound introducing requirement 2021-07-31 11:26:55 -05:00			note: required by a bound in `call_it`
Cleanup feature gates. 2022-01-19 09:24:49 -06:00			`--> $DIR/unboxed-closures-fnmut-as-fn.rs:22:14`
Use note to point at bound introducing requirement 2021-07-31 11:26:55 -05:00			`\|`
			`LL \| fn call_it<F:Fn(isize)->isize>(f: &F, x: isize) -> isize {`
			\| ^^^^^^^^^^^^^^^^ required by this bound in `call_it`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`

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