UI tests: add missing diagnostic kinds where possible

2025-04-08T20:06:31+00:00

Remove `Lexer`'s dependency on `Parser`.

2024-12-12T20:10:20+00:00

Lexing precedes parsing, as you'd expect: `Lexer` creates a `TokenStream` and `Parser` then parses that `TokenStream`. But, in a horrendous violation of layering abstractions and common sense, `Lexer` depends on `Parser`! The `Lexer::unclosed_delim_err` method does some error recovery that relies on creating a `Parser` to do some post-processing of the `TokenStream` that the `Lexer` just created. This commit just removes `unclosed_delim_err`. This change removes `Lexer`'s dependency on `Parser`, and also means that `lex_token_tree`'s return value can have a more typical form. The cost is slightly worse error messages in two obscure cases, as shown in these tests: - tests/ui/parser/brace-in-let-chain.rs: there is slightly less explanation in this case involving an extra `{`. - tests/ui/parser/diff-markers/unclosed-delims{,-in-macro}.rs: the diff marker detection is no longer supported (because that detection is implemented in the parser). In my opinion this cost is outweighed by the magnitude of the code cleanup.

Improve conflict marker recovery

2024-06-18T22:27:41+00:00

Show number in error message even for one error

2023-11-24T18:15:52+00:00

Co-authored-by: Adrian

When encountering unclosed delimiters during parsing, check for diff markers

2023-10-30T00:56:46+00:00

Fix #116252.

Move /src/test to /tests