Matthias Krüger 980bf1979e Rollup merge of #106859 - tialaramex:master, r=Nilstrieb ... Suggestion for type mismatch when we need a u8 but the programmer wrote a char literal Today Rust just points out that we have a char and we need a u8, but if I wrote 'A' then I could fix this by just writing b'A' instead. This code should detect the case where we're about to report a type mismatch of this kind, and the programmer wrote a char literal, and the char they wrote is ASCII, so therefore just prefixing b to make a byte literal will do what they meant. I have definitely written this mistake more than once, it's not difficult to figure out what to do, but the compiler might as well tell us anyway. I provided a test with two simple examples where the suggestion is appropriate, and one where it is not because the char literal is not ASCII, showing that the suggestion is only triggered in the former cases. I have contributed only a small typo doc fix before, so this is my first substantive rustc change.		2023-01-15 01:01:36 +01:00
..
src	Rollup merge of #106859 - tialaramex:master, r=Nilstrieb	2023-01-15 01:01:36 +01:00
Cargo.toml	Migrate OpaqueHiddenType, E0282, E0283, E0284, E0698	2022-08-23 14:47:07 +03:00