rust/tests/ui/span/multiline-span-simple.stderr

error[E0277]: cannot add `()` to `u32`
  --> $DIR/multiline-span-simple.rs:13:18
   |
LL |     foo(1 as u32 +
   |                  ^ no implementation for `u32 + ()`
   |
   = help: the trait `Add<()>` is not implemented for `u32`
   = help: the following other types implement trait `Add<Rhs>`:
             <&'a u32 as Add<u32>>
             <&u32 as Add<&u32>>
             <u32 as Add<&u32>>
             <u32 as Add>

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
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-20 03:57:10 +00:00			error[E0277]: cannot add `()` to `u32`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/multiline-span-simple.rs:13:18`
Show multiline spans in full if short enough When dealing with multiline spans that span few lines, show the complete span instead of restricting to the first character of the first line. For example, instead of: ``` % ./rustc foo.rs error[E0277]: the trait bound `{integer}: std::ops::Add<()>` is not satisfied --> foo.rs:13:9 \| 13 \| foo(1 + bar(x, \| ^ trait `{integer}: std::ops::Add<()>` not satisfied \| ``` show ``` % ./rustc foo.rs error[E0277]: the trait bound `{integer}: std::ops::Add<()>` is not satisfied --> foo.rs:13:9 \| 13 \| foo(1 + bar(x, \| ________^ starting here... 14 \| \| y), \| \|_____________^ ...ending here: trait `{integer}: std::ops::Add<()>` not satisfied \| ``` 2016-10-24 00:22:06 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| foo(1 as u32 +`
tests: fix fallout from changing the span of binop errors. 2017-05-29 11:55:54 +00:00			\| ^ no implementation for `u32 + ()`
Show multiline spans in full if short enough When dealing with multiline spans that span few lines, show the complete span instead of restricting to the first character of the first line. For example, instead of: ``` % ./rustc foo.rs error[E0277]: the trait bound `{integer}: std::ops::Add<()>` is not satisfied --> foo.rs:13:9 \| 13 \| foo(1 + bar(x, \| ^ trait `{integer}: std::ops::Add<()>` not satisfied \| ``` show ``` % ./rustc foo.rs error[E0277]: the trait bound `{integer}: std::ops::Add<()>` is not satisfied --> foo.rs:13:9 \| 13 \| foo(1 + bar(x, \| ________^ starting here... 14 \| \| y), \| \|_____________^ ...ending here: trait `{integer}: std::ops::Add<()>` not satisfied \| ``` 2016-10-24 00:22:06 +00: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 07:40:56 +00:00			= help: the trait `Add<()>` is not implemented for `u32`
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>`:
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 22:24:48 +00:00			`<&'a u32 as Add<u32>>`
			`<&u32 as Add<&u32>>`
Use `TraitRef::to_string` sorting in favor of `TraitRef::ord`, as the latter compares `DefId`s which we need to avoid 2024-03-21 12:55:28 +00:00			`<u32 as Add<&u32>>`
			`<u32 as Add>`
Show multiline spans in full if short enough When dealing with multiline spans that span few lines, show the complete span instead of restricting to the first character of the first line. For example, instead of: ``` % ./rustc foo.rs error[E0277]: the trait bound `{integer}: std::ops::Add<()>` is not satisfied --> foo.rs:13:9 \| 13 \| foo(1 + bar(x, \| ^ trait `{integer}: std::ops::Add<()>` not satisfied \| ``` show ``` % ./rustc foo.rs error[E0277]: the trait bound `{integer}: std::ops::Add<()>` is not satisfied --> foo.rs:13:9 \| 13 \| foo(1 + bar(x, \| ________^ starting here... 14 \| \| y), \| \|_____________^ ...ending here: trait `{integer}: std::ops::Add<()>` not satisfied \| ``` 2016-10-24 00:22:06 +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`
Show multiline spans in full if short enough When dealing with multiline spans that span few lines, show the complete span instead of restricting to the first character of the first line. For example, instead of: ``` % ./rustc foo.rs error[E0277]: the trait bound `{integer}: std::ops::Add<()>` is not satisfied --> foo.rs:13:9 \| 13 \| foo(1 + bar(x, \| ^ trait `{integer}: std::ops::Add<()>` not satisfied \| ``` show ``` % ./rustc foo.rs error[E0277]: the trait bound `{integer}: std::ops::Add<()>` is not satisfied --> foo.rs:13:9 \| 13 \| foo(1 + bar(x, \| ________^ starting here... 14 \| \| y), \| \|_____________^ ...ending here: trait `{integer}: std::ops::Add<()>` not satisfied \| ``` 2016-10-24 00:22:06 +00:00
update tests 2018-03-03 14:59:40 +00:00			For more information about this error, try `rustc --explain E0277`.