mirror of
https://github.com/rust-lang/rust
synced 2024-09-06 01:11:17 +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.
10 lines
279 B
Plaintext
10 lines
279 B
Plaintext
error[E0432]: unresolved import `self::*`
|
|
--> $DIR/issue-31212.rs:5:13
|
|
|
|
|
LL | pub use self::*;
|
|
| ^^^^^^^ cannot glob-import a module into itself
|
|
|
|
error: aborting due to 1 previous error
|
|
|
|
For more information about this error, try `rustc --explain E0432`.
|