Nicholas Nethercote 306612ea60 Be more careful about interpreting a label/lifetime as a mistyped char literal. ... Currently the parser will interpret any label/lifetime in certain positions as a mistyped char literal, on the assumption that the trailing single quote was accidentally omitted. This is reasonable for a something like 'a (because 'a' would be valid) but not reasonable for a something like 'abc (because 'abc' is not valid). This commit restricts this behaviour only to labels/lifetimes that would be valid char literals, via the new `could_be_unclosed_char_literal` function. The commit also augments the `label-is-actually-char.rs` test in a couple of ways: - Adds testing of labels/lifetimes with identifiers longer than one char, e.g. 'abc. - Adds a new match with simpler patterns, because the `recover_unclosed_char` call in `parse_pat_with_range_pat` was not being exercised (in this test or any other ui tests). Fixes #120397, an assertion failure, which was caused by this behaviour in the parser interacting with some new stricter char literal checking added in #120329.		2024-01-29 11:25:09 +11:00
..
src	Be more careful about interpreting a label/lifetime as a mistyped char literal.	2024-01-29 11:25:09 +11:00
Cargo.toml	Update to bitflags 2 in the compiler	2023-12-30 18:17:28 +01:00
messages.ftl	Rollup merge of #119062 - compiler-errors:asm-in-let-else, r=davidtwco,est31	2024-01-19 08:15:03 +01:00