rust/tests/ui/parser/raw, branch auto

cleaned up some tests

2025-07-04T19:45:24+00:00

moved tests

2025-07-01T13:21:05+00:00

UI tests: add missing diagnostic kinds where possible

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

fix rebase

2025-03-07T17:55:08+00:00

Refactor `emitter` to better account for unicode chars when trimming

2025-03-07T17:55:08+00:00

Change the way that underline positions are calculated by delaying using the "visual" column position until the last possible moment, instead using the "file"/byte position in the file, and then calculating visual positioning as late as possible. This should make the underlines more resilient to non-1-width unicode chars. Unfortunately, as part of this change (which fixes some visual bugs) comes with the loss of some eager tab codepoint handling, but the output remains legible despite some minor regression on the "margin trimming" logic.

On long spans, trim the middle of them to make them fit in the terminal width

2025-03-07T17:55:08+00:00

When encountering a single line span that is wider than the terminal, we keep context at the start and end of the span but otherwise remove the code from the middle. This is somewhat independent from whether the left and right margins of the output have been trimmed as well. ``` error[E0308]: mismatched types --> $DIR/long-span.rs:6:15 | LL | ... = [0, 0, 0, 0, ..., 0, 0]; | ^^^^^^^^^^^^^...^^^^^^^ expected `u8`, found `[{integer}; 1681]` ``` Address part of #137680 (missing handling of the long suggestion). Fix #125581.

Fix const items not being allowed to be called `r#move` or `r#static`

2025-02-16T17:21:40+00:00

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.

Replace ASCII control chars with Unicode Control Pictures

2024-07-18T19:23:42+00:00

``` error: bare CR not allowed in doc-comment --> $DIR/lex-bare-cr-string-literal-doc-comment.rs:3:32 | LL | /// doc comment with bare CR: '␍' | ^ ```

[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives

2024-02-16T20:02:50+00:00

Show number in error message even for one error

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

Co-authored-by: Adrian