rust/tests/ui/pattern/pattern-tyvar-2.stderr

error[E0369]: cannot multiply `Vec<isize>` by `{integer}`
  --> $DIR/pattern-tyvar-2.rs:3:71
   |
LL | fn foo(t: Bar) -> isize { match t { Bar::T1(_, Some(x)) => { return x * 3; } _ => { panic!(); } } }
   |                                                                     - ^ - {integer}
   |                                                                     |
   |                                                                     Vec<isize>
   |
note: the foreign item type `Vec<isize>` doesn't implement `Mul<{integer}>`
  --> $SRC_DIR/alloc/src/vec/mod.rs:LL:COL
   |
   = note: not implement `Mul<{integer}>`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0369`.
Improve wording of "cannot multiply" type error For example, if you had this code: fn foo(x: i32, y: f32) -> f32 { x * y } You would get this error: error[E0277]: cannot multiply `f32` to `i32` --> src/lib.rs:2:7 \| 2 \| x * y \| ^ no implementation for `i32 * f32` \| = help: the trait `Mul<f32>` is not implemented for `i32` However, that's not usually how people describe multiplication. People usually describe multiplication like how the division error words it: error[E0277]: cannot divide `i32` by `f32` --> src/lib.rs:2:7 \| 2 \| x / y \| ^ no implementation for `i32 / f32` \| = help: the trait `Div<f32>` is not implemented for `i32` So that's what this change does. It changes this: error[E0277]: cannot multiply `f32` to `i32` --> src/lib.rs:2:7 \| 2 \| x * y \| ^ no implementation for `i32 * f32` \| = help: the trait `Mul<f32>` is not implemented for `i32` To this: error[E0277]: cannot multiply `i32` by `f32` --> src/lib.rs:2:7 \| 2 \| x * y \| ^ no implementation for `i32 * f32` \| = help: the trait `Mul<f32>` is not implemented for `i32` 2020-10-17 19:59:51 -07:00			error[E0369]: cannot multiply `Vec<isize>` by `{integer}`
Better diagnostic for binary operation on BoxedValues 2019-03-27 13:13:09 -04:00			`--> $DIR/pattern-tyvar-2.rs:3:71`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			`LL \| fn foo(t: Bar) -> isize { match t { Bar::T1(_, Some(x)) => { return x * 3; } _ => { panic!(); } } }`
Better diagnostic for binary operation on BoxedValues 2019-03-27 13:13:09 -04:00			`\| - ^ - {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			`\| Vec<isize>`
Change E0369 diagnostic give note information for foreign items. Make it easy for developers to understand why the binop cannot be applied. fixes #125631 2024-06-25 10:00:30 +08:00			`\|`
			note: the foreign item type `Vec<isize>` doesn't implement `Mul<{integer}>`
			`--> $SRC_DIR/alloc/src/vec/mod.rs:LL:COL`
			`\|`
			= note: not implement `Mul<{integer}>`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02: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`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			For more information about this error, try `rustc --explain E0369`.