os-rust/tests/ui/imports/issue-31212.stderr

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`.
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			error[E0432]: unresolved import `self::*`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-31212.rs:5:13`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| pub use self::*;`
use structured suggestions for E0432 2019-01-16 15:30:41 -05:00			`\| ^^^^^^^ cannot glob-import a module into itself`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
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 19:12:05 +00:00			`error: aborting due to 1 previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
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 19:12:05 +00:00			For more information about this error, try `rustc --explain E0432`.