rust/tests/ui/imports/import-from-missing-star.rs

use spam::*; //~ ERROR unresolved import `spam` [E0432]

fn main() {
    // Expect these to pass because the compiler knows there's a failed `*` import that might have
    // caused it.
    ham();
    eggs();
    // Even this case, as we might have expected `spam::foo` to exist.
    foo::bar();
}
Silence some resolve errors when there have been glob import errors When encountering `use foo::;` where `foo` fails to be found, and we later encounter resolution errors, we silence those later errors. A single case of the above, for an existing* import on a big codebase would otherwise have a huge number of knock-down spurious errors. Ideally, instead of a global flag to silence all subsequent resolve errors, we'd want to introduce an unameable binding in the appropriate rib as a sentinel when there's a failed glob import, so when we encounter a resolve error we can search for that sentinel and if found, and only then, silence that error. The current approach is just a quick proof of concept to iterate over. Partially address #96799. 2024-05-21 14:12:05 -05:00			use spam::*; //~ ERROR unresolved import `spam` [E0432]

			`fn main() {`
			// Expect these to pass because the compiler knows there's a failed `*` import that might have
			`// caused it.`
			`ham();`
			`eggs();`
			// Even this case, as we might have expected `spam::foo` to exist.
			`foo::bar();`
			`}`