os-rust/tests/ui/issues/issue-11771.stderr

error[E0277]: cannot add `()` to `{integer}`
  --> $DIR/issue-11771.rs:3:7
   |
LL |     1 +
   |       ^ no implementation for `{integer} + ()`
   |
   = help: the trait `Add<()>` is not implemented for `{integer}`
   = help: the following other types implement trait `Add<Rhs>`:
             `&f128` implements `Add<f128>`
             `&f128` implements `Add`
             `&f16` implements `Add<f16>`
             `&f16` implements `Add`
             `&f32` implements `Add<f32>`
             `&f32` implements `Add`
             `&f64` implements `Add<f64>`
             `&f64` implements `Add`
           and 56 others

error[E0277]: cannot add `()` to `{integer}`
  --> $DIR/issue-11771.rs:8:7
   |
LL |     1 +
   |       ^ no implementation for `{integer} + ()`
   |
   = help: the trait `Add<()>` is not implemented for `{integer}`
   = help: the following other types implement trait `Add<Rhs>`:
             `&f128` implements `Add<f128>`
             `&f128` implements `Add`
             `&f16` implements `Add<f16>`
             `&f16` implements `Add`
             `&f32` implements `Add<f32>`
             `&f32` implements `Add`
             `&f64` implements `Add<f64>`
             `&f64` implements `Add`
           and 56 others

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0277`.
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			error[E0277]: cannot add `()` to `{integer}`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-11771.rs:3:7`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
			`LL \| 1 +`
			\| ^ no implementation for `{integer} + ()`
			`\|`
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 `Add<()>` is not implemented for `{integer}`
Refer to the TraitRef::identity in the message to be clearer 2022-03-27 02:02:07 +00:00			= help: the following other types implement trait `Add<Rhs>`:
Don't call const normalize in error reporting 2024-09-22 13:52:20 -04:00			`&f128` implements `Add<f128>`
			`&f128` implements `Add`
			`&f16` implements `Add<f16>`
			`&f16` implements `Add`
			`&f32` implements `Add<f32>`
			`&f32` implements `Add`
			`&f64` implements `Add<f64>`
			`&f64` implements `Add`
Add basic library support for `f16` and `f128` Implement basic operation traits that get lowered to intrinsics. This includes codegen tests for implemented operations. 2024-03-06 05:40:29 -06:00			`and 56 others`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			error[E0277]: cannot add `()` to `{integer}`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-11771.rs:8:7`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
			`LL \| 1 +`
			\| ^ no implementation for `{integer} + ()`
			`\|`
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 `Add<()>` is not implemented for `{integer}`
Refer to the TraitRef::identity in the message to be clearer 2022-03-27 02:02:07 +00:00			= help: the following other types implement trait `Add<Rhs>`:
Don't call const normalize in error reporting 2024-09-22 13:52:20 -04:00			`&f128` implements `Add<f128>`
			`&f128` implements `Add`
			`&f16` implements `Add<f16>`
			`&f16` implements `Add`
			`&f32` implements `Add<f32>`
			`&f32` implements `Add`
			`&f64` implements `Add<f64>`
			`&f64` implements `Add`
Add basic library support for `f16` and `f128` Implement basic operation traits that get lowered to intrinsics. This includes codegen tests for implemented operations. 2024-03-06 05:40:29 -06:00			`and 56 others`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			`error: aborting due to 2 previous errors`

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