rust/tests/ui/impl-trait/equality.stderr

warning: the feature `specialization` is incomplete and may not be safe to use and/or cause compiler crashes
  --> $DIR/equality.rs:1:12
   |
LL | #![feature(specialization)]
   |            ^^^^^^^^^^^^^^
   |
   = note: see issue #31844 <https://github.com/rust-lang/rust/issues/31844> for more information
   = help: consider using `min_specialization` instead, which is more stable and complete
   = note: `#[warn(incomplete_features)]` on by default

error[E0308]: mismatched types
  --> $DIR/equality.rs:15:5
   |
LL | fn two(x: bool) -> impl Foo {
   |                    -------- expected `i32` because of return type
...
LL |     0_u32
   |     ^^^^^ expected `i32`, found `u32`
   |
help: change the type of the numeric literal from `u32` to `i32`
   |
LL |     0_i32
   |       ~~~

error[E0277]: cannot add `impl Foo` to `u32`
  --> $DIR/equality.rs:24:11
   |
LL |         n + sum_to(n - 1)
   |           ^ no implementation for `u32 + impl Foo`
   |
   = help: the trait `Add<impl Foo>` is not implemented for `u32`
   = help: the following other types implement trait `Add<Rhs>`:
             <u32 as Add>
             <u32 as Add<&u32>>
             <&'a u32 as Add<u32>>
             <&u32 as Add<&u32>>

error: aborting due to 2 previous errors; 1 warning emitted

Some errors have detailed explanations: E0277, E0308.
For more information about an error, try `rustc --explain E0277`.
warn against 'specialization' feature 2020-05-17 03:22:48 -05:00			warning: the feature `specialization` is incomplete and may not be safe to use and/or cause compiler crashes
			`--> $DIR/equality.rs:1:12`
			`\|`
			`LL \| #![feature(specialization)]`
			`\| ^^^^^^^^^^^^^^`
			`\|`
			`= note: see issue #31844 <https://github.com/rust-lang/rust/issues/31844> for more information`
Suggest minimal subset features in `incomplete_features` lint 2020-10-13 18:35:32 -05:00			= help: consider using `min_specialization` instead, which is more stable and complete
bless ui tests 2022-09-18 10:55:36 -05:00			= note: `#[warn(incomplete_features)]` on by default
warn against 'specialization' feature 2020-05-17 03:22:48 -05:00
Explicit help message for binop type missmatch When trying to do a binary operation with missing implementation, for example `1 + Some(2)`, provide an explicit help message: ``` note: no implementation for `{integer} + std::option::Option<{integer}>` ``` Use `rustc_on_unimplemented` for the suggestions. Move cfail test to ui. 2017-04-10 16:17:49 -05:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/equality.rs:15:5`
Explicit help message for binop type missmatch When trying to do a binary operation with missing implementation, for example `1 + Some(2)`, provide an explicit help message: ``` note: no implementation for `{integer} + std::option::Option<{integer}>` ``` Use `rustc_on_unimplemented` for the suggestions. Move cfail test to ui. 2017-04-10 16:17:49 -05:00			`\|`
Eagerly merge hidden types. 2022-01-26 08:47:03 -06:00			`LL \| fn two(x: bool) -> impl Foo {`
Resolve vars before emitting coerce error 2022-08-03 22:05:57 -05:00			\| -------- expected `i32` because of return type
Revert "Auto merge of #93893 - oli-obk:sad_revert, r=oli-obk" This reverts commit 6499c5e7fc173a3f55b7a3bd1e6a50e9edef782d, reversing changes made to 78450d2d602b06d9b94349aaf8cece1a4acaf3a8. 2022-02-14 10:10:22 -06:00			`...`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| 0_u32`
Surround types with backticks in type errors 2019-11-15 11:37:01 -06:00			\| ^^^^^ expected `i32`, found `u32`
Resolve vars before emitting coerce error 2022-08-03 22:05:57 -05:00			`\|`
			help: change the type of the numeric literal from `u32` to `i32`
			`\|`
			`LL \| 0_i32`
			`\| ~~~`
Explicit help message for binop type missmatch When trying to do a binary operation with missing implementation, for example `1 + Some(2)`, provide an explicit help message: ``` note: no implementation for `{integer} + std::option::Option<{integer}>` ``` Use `rustc_on_unimplemented` for the suggestions. Move cfail test to ui. 2017-04-10 16:17:49 -05:00
Add filtering options to `rustc_on_unimplemented` - filter error on the evaluated value of `Self` - filter error on the evaluated value of the type arguments - add argument to include custom note in diagnostic - allow the parser to parse `Self` when processing attributes - add custom message to binops 2018-01-19 21:57:10 -06:00			error[E0277]: cannot add `impl Foo` to `u32`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/equality.rs:24:11`
Explicit help message for binop type missmatch When trying to do a binary operation with missing implementation, for example `1 + Some(2)`, provide an explicit help message: ``` note: no implementation for `{integer} + std::option::Option<{integer}>` ``` Use `rustc_on_unimplemented` for the suggestions. Move cfail test to ui. 2017-04-10 16:17:49 -05:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| n + sum_to(n - 1)`
tests: fix fallout from changing the span of binop errors. 2017-05-29 06:55:54 -05:00			\| ^ no implementation for `u32 + impl Foo`
Explicit help message for binop type missmatch When trying to do a binary operation with missing implementation, for example `1 + Some(2)`, provide an explicit help message: ``` note: no implementation for `{integer} + std::option::Option<{integer}>` ``` Use `rustc_on_unimplemented` for the suggestions. Move cfail test to ui. 2017-04-10 16:17:49 -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 `Add<impl Foo>` is not implemented for `u32`
Refer to the TraitRef::identity in the message to be clearer 2022-03-26 21:02:07 -05:00			= help: the following other types implement trait `Add<Rhs>`:
Don't sort strings right after we just sorted by types 2023-06-27 18:31:06 -05:00			`<u32 as Add>`
			`<u32 as Add<&u32>>`
Tweak "the following other types implement trait" When any of the suggested impls is an exact match, only show the exact matches. This is particularly relevant for integer types. fix fmt 2022-12-05 16:24:48 -06:00			`<&'a u32 as Add<u32>>`
			`<&u32 as Add<&u32>>`
Explicit help message for binop type missmatch When trying to do a binary operation with missing implementation, for example `1 + Some(2)`, provide an explicit help message: ``` note: no implementation for `{integer} + std::option::Option<{integer}>` ``` Use `rustc_on_unimplemented` for the suggestions. Move cfail test to ui. 2017-04-10 16:17:49 -05:00
skip pointing out ambuguous impls in alloc/std crates too 2022-01-29 17:34:06 -06:00			`error: aborting due to 2 previous errors; 1 warning emitted`
Explicit help message for binop type missmatch When trying to do a binary operation with missing implementation, for example `1 + Some(2)`, provide an explicit help message: ``` note: no implementation for `{integer} + std::option::Option<{integer}>` ``` Use `rustc_on_unimplemented` for the suggestions. Move cfail test to ui. 2017-04-10 16:17:49 -05:00
skip pointing out ambuguous impls in alloc/std crates too 2022-01-29 17:34:06 -06:00			`Some errors have detailed explanations: E0277, E0308.`
update tests 2018-03-03 08:59:40 -06:00			For more information about an error, try `rustc --explain E0277`.