rust/tests/ui/diagnostic-width, branch beta

Account for bare tuples in field searching logic

2025-08-07T21:39:00+00:00

When looking for the field names and types of a given type, account for tuples. This allows suggestions for incorrectly nested field accesses and field name typos to trigger as intended. Previously these suggestions only worked on `ty::Adt`, including tuple structs which are no different to tuples, so they should behave the same in suggestions. ``` error[E0599]: no method named `get_ref` found for tuple `(BufReader,)` in the current scope --> $DIR/missing-field-access.rs:11:15 | LL | let x = f.get_ref(); | ^^^^^^^ method not found in `(BufReader,)` | help: one of the expressions' fields has a method of the same name | LL | let x = f.0.get_ref(); | ++ ```

Bless unicode test

2025-06-16T11:30:09+00:00

Most likely caused by updating unicode-width v0.2.0 -> v0.2.1, the change seems reasonable enough.

cleaned up some tests

2025-06-07T20:14:05+00:00

cleaned up some tests

2025-06-05T15:03:29+00:00

compiletest: Support matching on non-json lines in compiler output

2025-05-04T15:27:45+00:00

and migrate most of remaining `error-pattern`s to it.

compiletest: Make diagnostic kind mandatory on line annotations

2025-04-30T07:44:24+00:00

Do not suggest using `-Zmacro-backtrace` for builtin macros

2025-03-14T19:50:03+00:00

For macros that are implemented on the compiler, we do *not* mention the `-Zmacro-backtrace` flag. This includes `derive`s and standard macros.

Make trimming logic work on more than one span at a time

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.