rust/tests/ui/unresolved, branch try-perf

Use non-2015 edition paths in tests that do not test for their resolution

2025-06-05T07:19:31+00:00

Note potential but private items in show_candidates

2025-03-22T03:41:42+00:00

Signed-off-by: xizheyin

Trim suggestion parts to the subset that is purely additive

2025-02-14T08:44:10+00:00

Consider add-prefix replacements too

2025-02-14T08:27:17+00:00

Show diff suggestion format on verbose replacement

2025-02-10T20:21:39+00:00

``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 | LL | let _ = 2.l; | ^ | help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix | LL - let _ = 2.l; LL + let _ = 2.0f64; | ```

Reword "crate not found" resolve message

2025-01-24T01:19:50+00:00

``` error[E0432]: unresolved import `some_novel_crate` --> file.rs:1:5 | 1 | use some_novel_crate::Type; | ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `some_novel_crate` ``` On resolve errors where there might be a missing crate, mention `cargo add foo`: ``` error[E0433]: failed to resolve: use of unresolved module or unlinked crate `nope` --> $DIR/conflicting-impl-with-err.rs:4:11 | LL | impl From for Error { | ^^^^ use of unresolved module or unlinked crate `nope` | = help: if you wanted to use a crate named `nope`, use `cargo add nope` to add it to your `Cargo.toml` ```

Structured suggestion for `extern crate foo` when `foo` isn't resolved in import

2024-07-29T23:49:51+00:00

When encountering a name in an import that could have come from a crate that wasn't imported, use a structured suggestion to suggest `extern crate foo;` pointing at the right place in the crate. When encountering `_` in an import, do not suggest `extern crate _;`. ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ maybe a missing crate `spam`? | help: consider importing the `spam` crate | LL + extern crate spam; | ```

Do not use question as label

2024-07-24T21:03:27+00:00

We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```

[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