rust/tests/ui/extern/extern-crate-visibility.stderr

error[E0603]: crate import `core` is private
  --> $DIR/extern-crate-visibility.rs:6:10
   |
LL | use foo::core::cell;
   |          ^^^^ private crate import
   |
note: the crate import `core` is defined here
  --> $DIR/extern-crate-visibility.rs:2:5
   |
LL |     extern crate core;
   |     ^^^^^^^^^^^^^^^^^^
help: consider importing this module instead
   |
LL | use std::cell;
   |     ~~~~~~~~~

error[E0603]: crate import `core` is private
  --> $DIR/extern-crate-visibility.rs:9:10
   |
LL |     foo::core::cell::Cell::new(0);
   |          ^^^^ private crate import
   |
note: the crate import `core` is defined here
  --> $DIR/extern-crate-visibility.rs:2:5
   |
LL |     extern crate core;
   |     ^^^^^^^^^^^^^^^^^^
help: consider importing this struct instead
   |
LL |     std::cell::Cell::new(0);
   |     ~~~~~~~~~~~~~~~

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0603`.
resolve: Say "import" when reporting private imports 2020-01-12 07:20:57 -06:00			error[E0603]: crate import `core` is private
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/extern-crate-visibility.rs:6:10`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| use foo::core::cell;`
Normalize wording of privacy access labels 2020-03-22 17:36:54 -05:00			`\| ^^^^ private crate import`
resolve: Point at the private item definitions in privacy errors 2020-01-12 07:04:03 -06:00			`\|`
resolve: Say "import" when reporting private imports 2020-01-12 07:20:57 -06:00			note: the crate import `core` is defined here
resolve: Point at the private item definitions in privacy errors 2020-01-12 07:04:03 -06:00			`--> $DIR/extern-crate-visibility.rs:2:5`
			`\|`
			`LL \| extern crate core;`
			`\| ^^^^^^^^^^^^^^^^^^`
Tweak privacy errors to account for reachable items Suggest publicly accessible paths for items in private mod: When encountering a path in non-import situations that are not reachable due to privacy constraints, search for any public re-exports that the user could use instead. Track whether an import suggestion is offering a re-export. When encountering a path with private segments, mention if the item at the final path segment is not publicly accessible at all. Add item visibility metadata to privacy errors from imports: On unreachable imports, record the item that was being imported in order to suggest publicly available re-exports or to be explicit that the item is not available publicly from any path. In order to allow this, we add a mode to `resolve_path` that will not add new privacy errors, nor return early if it encounters one. This way we can get the `Res` corresponding to the final item in the import, which is used in the privacy error machinery. 2023-06-16 14:44:06 -05:00			`help: consider importing this module instead`
			`\|`
			`LL \| use std::cell;`
			`\| ~~~~~~~~~`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
resolve: Say "import" when reporting private imports 2020-01-12 07:20:57 -06:00			error[E0603]: crate import `core` is private
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/extern-crate-visibility.rs:9:10`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| foo::core::cell::Cell::new(0);`
Normalize wording of privacy access labels 2020-03-22 17:36:54 -05:00			`\| ^^^^ private crate import`
resolve: Point at the private item definitions in privacy errors 2020-01-12 07:04:03 -06:00			`\|`
resolve: Say "import" when reporting private imports 2020-01-12 07:20:57 -06:00			note: the crate import `core` is defined here
resolve: Point at the private item definitions in privacy errors 2020-01-12 07:04:03 -06:00			`--> $DIR/extern-crate-visibility.rs:2:5`
			`\|`
			`LL \| extern crate core;`
			`\| ^^^^^^^^^^^^^^^^^^`
Tweak privacy errors to account for reachable items Suggest publicly accessible paths for items in private mod: When encountering a path in non-import situations that are not reachable due to privacy constraints, search for any public re-exports that the user could use instead. Track whether an import suggestion is offering a re-export. When encountering a path with private segments, mention if the item at the final path segment is not publicly accessible at all. Add item visibility metadata to privacy errors from imports: On unreachable imports, record the item that was being imported in order to suggest publicly available re-exports or to be explicit that the item is not available publicly from any path. In order to allow this, we add a mode to `resolve_path` that will not add new privacy errors, nor return early if it encounters one. This way we can get the `Res` corresponding to the final item in the import, which is used in the privacy error machinery. 2023-06-16 14:44:06 -05:00			`help: consider importing this struct instead`
			`\|`
			`LL \| std::cell::Cell::new(0);`
			`\| ~~~~~~~~~~~~~~~`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to 2 previous errors`

			For more information about this error, try `rustc --explain E0603`.