5 commits

Author	SHA1	Message	Date
Esteban Küber	c73b3d20c6	Unify wording of resolve error ... Remove "failed to resolve" and use the same format we use in other resolution errors "cannot find `name`". ``` error[E0433]: cannot find `nonexistent` in `existent` --> $DIR/custom_attr_multisegment_error.rs:5:13 | LL | #[existent::nonexistent] | ^^^^^^^^^^^ could not find `nonexistent` in `existent` ```	2026-02-17 16:51:44 +00:00
Ben Kimock	7dfc786df1	Enable more tests on Windows	2025-02-03 10:39:32 -05:00
Esteban Küber	dd52bfc76e	Reword "crate not found" resolve message ... ``` 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<nope::Thing> 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` ```	2025-01-24 01:19:50 +00:00
许杰友 Jieyou Xu (Joe)	ec2cc761bc	[AUTO-GENERATED] Migrate ui tests from // to //@ directives	2024-02-16 20:02:50 +00:00
Albert Larsan	cf2dff2b1e	Move /src/test to /tests	2023-01-11 09:32:08 +00:00

Renamed from src/test/ui/parser/mod_file_not_exist.rs (Browse further)