rust/tests/ui/issues/issue-52717.rs

enum A {
  A {
    foo: usize,
  }
}

fn main() {
  let x = A::A { foo: 3 };
  match x {
    A::A { fob } => { println!("{}", fob); }
//~^ ERROR does not have a field named `fob`
  }
}
Fixed: Multiple errors on single typo in match pattern Here we have fixed the case where we were throwing two diagnostic messages `E0026` and `E0027` for same case like this Example error[E0026]: variant `A::A` does not have a field named `fob` --> src/test/ui/issue-52717.rs:20:12 \| 20 \| A::A { fob } => { println!("{}", fob); } \| ^^^ variant `A::A` does not have this field error[E0027]: pattern does not mention field `foo` --> src/test/ui/issue-52717.rs:20:5 \| 20 \| A::A { fob } => { println!("{}", fob); } \| ^^^^^^^^^^^^ missing field `foo` error: aborting due to 2 previous errors Here above we can see that both `E0026` and `E0027` are depicting same thing. So, to fix this issue, we are simply checking element of `inexistent_fields` is there any value lies in `unmentioned_fields` using Levenshtein algorithm, if does then for that case we are simply deleting element from `unmentioned_fields`. More or less now instead of showing separate message in `E0027` we are giving extra hint on `E0026` Address: #52717 2018-10-19 10:33:49 +00:00			`enum A {`
			`A {`
			`foo: usize,`
			`}`
			`}`

			`fn main() {`
			`let x = A::A { foo: 3 };`
			`match x {`
			`A::A { fob } => { println!("{}", fob); }`
Update tests 2018-11-27 09:56:36 +00:00			//~^ ERROR does not have a field named `fob`
Fixed: Multiple errors on single typo in match pattern Here we have fixed the case where we were throwing two diagnostic messages `E0026` and `E0027` for same case like this Example error[E0026]: variant `A::A` does not have a field named `fob` --> src/test/ui/issue-52717.rs:20:12 \| 20 \| A::A { fob } => { println!("{}", fob); } \| ^^^ variant `A::A` does not have this field error[E0027]: pattern does not mention field `foo` --> src/test/ui/issue-52717.rs:20:5 \| 20 \| A::A { fob } => { println!("{}", fob); } \| ^^^^^^^^^^^^ missing field `foo` error: aborting due to 2 previous errors Here above we can see that both `E0026` and `E0027` are depicting same thing. So, to fix this issue, we are simply checking element of `inexistent_fields` is there any value lies in `unmentioned_fields` using Levenshtein algorithm, if does then for that case we are simply deleting element from `unmentioned_fields`. More or less now instead of showing separate message in `E0027` we are giving extra hint on `E0026` Address: #52717 2018-10-19 10:33:49 +00:00			`}`
			`}`