Noratrieb 8a02724b9d Fix const items not being allowed to be called r#move or r#static ... Because of an ambiguity with const closures, the parser needs to ensure that for a const item, the `const` keyword isn't followed by a `move` or `static` keyword, as that would indicate a const closure: ```rust fn main() { const move // ... } ``` This check did not take raw identifiers into account, therefore being unable to distinguish between `const move` and `const r#move`. The latter is obviously not a const closure, so it should be allowed as a const item. This fixes the check in the parser to only treat `const ...` as a const closure if it's followed by the *proper keyword*, and not a raw identifier. Additionally, this adds a large test that tests for all raw identifiers in all kinds of positions, including `const`, to prevent issues like this one from occurring again.		2025-02-16 18:21:40 +01:00
..
src	Fix const items not being allowed to be called r#move or r#static	2025-02-16 18:21:40 +01:00
Cargo.toml	Update unicode-width to 0.2.0	2024-10-12 21:57:50 +00:00
messages.ftl	Try to recover from path sep error in parser	2025-02-15 07:44:20 +08:00