mirror of
https://github.com/rust-lang/rust
synced 2024-10-01 06:14:33 +00:00
37c54db477
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.
13 lines
408 B
Rust
13 lines
408 B
Rust
mod foo {
|
|
use spam::*; //~ ERROR unresolved import `spam` [E0432]
|
|
}
|
|
|
|
fn main() {
|
|
// Expect this to pass because the compiler knows there's a failed `*` import in `foo` that
|
|
// might have caused it.
|
|
foo::bar();
|
|
// FIXME: these two should *fail* because they can't be fixed by fixing the glob import in `foo`
|
|
ham(); // should error but doesn't
|
|
eggs(); // should error but doesn't
|
|
}
|