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

enum Bar { T1((), Option<Vec<isize>>), T2, }

fn foo(t: Bar) -> isize { match t { Bar::T1(_, Some(x)) => { return x * 3; } _ => { panic!(); } } }
//~^ ERROR cannot multiply `Vec<isize>` by `{integer}`

fn main() { }
make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			`enum Bar { T1((), Option<Vec<isize>>), T2, }`
Two tests that the typechecker correctly unifies type arguments in patterns with their expected tag types 2011-05-14 19:03:08 -07:00
make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			`fn foo(t: Bar) -> isize { match t { Bar::T1(_, Some(x)) => { return x * 3; } _ => { panic!(); } } }`
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 cannot multiply `Vec<isize>` by `{integer}`
Two tests that the typechecker correctly unifies type arguments in patterns with their expected tag types 2011-05-14 19:03:08 -07:00
Port the tests to the typaram foo<T> syntax. 2011-08-10 09:27:22 -07:00			`fn main() { }`