os-rust/src/test/ui/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}`
   |
   = help: the trait `FnOnce<()>` is not implemented for `{integer}`
   = note: wrap the `{integer}` in a closure with no arguments: `|| { /* code */ }`

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 10:40:56 +03:00			error[E0277]: expected a `FnOnce<()>` closure, found `{integer}`
When possible point at argument causing item obligation failure 2019-09-15 21:58:20 -07:00			`--> $DIR/closure-expected.rs:3:23`
When closure with no arguments was expected, suggest wrapping 2018-08-12 12:21:53 -07:00			`\|`
			`LL \| let y = x.or_else(4);`
When possible point at argument causing item obligation failure 2019-09-15 21:58:20 -07:00			\| ^ expected an `FnOnce<()>` closure, found `{integer}`
When closure with no arguments was expected, suggest wrapping 2018-08-12 12:21:53 -07: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 10:40:56 +03:00			= help: the trait `FnOnce<()>` is not implemented for `{integer}`
Add missing backticks in diagnostics note 2020-07-23 21:52:48 +09:00			= note: wrap the `{integer}` in a closure with no arguments: `\|\| { /* code */ }`
When closure with no arguments was expected, suggest wrapping 2018-08-12 12:21:53 -07:00
			`error: aborting due to previous error`

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