rust/tests/ui/rfc-2126-extern-absolute-paths/not-allowed.stderr

error[E0432]: unresolved import `alloc`
  --> $DIR/not-allowed.rs:5:5
   |
LL | use alloc;
   |     ^^^^^ no external crate `alloc`
   |
help: consider importing one of these items instead
   |
LL | use core::alloc;
   |     ~~~~~~~~~~~
LL | use std::alloc;
   |     ~~~~~~~~~~

error: aborting due to previous error

For more information about this error, try `rustc --explain E0432`.
rustc_resolve: always include core, std and meta in the extern prelude. 2018-09-10 19:41:30 +03:00			error[E0432]: unresolved import `alloc`
Avoid "whitelist" Other terms are more inclusive and precise. 2020-07-07 11:12:44 -04:00			`--> $DIR/not-allowed.rs:5:5`
rustc_resolve: always include core, std and meta in the extern prelude. 2018-09-10 19:41:30 +03:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| use alloc;`
Improve wording for external crate resolution error I think it reads better this way. 2020-09-30 15:52:13 -07:00			\| ^^^^^ no external crate `alloc`
suggest candidates for unresolved import 2022-10-10 11:14:32 +08:00			`\|`
			`help: consider importing one of these items instead`
			`\|`
			`LL \| use core::alloc;`
			`\| ~~~~~~~~~~~`
Fix use suggestion span 2023-01-17 02:35:47 +00:00			`LL \| use std::alloc;`
			`\| ~~~~~~~~~~`
rustc_resolve: always include core, std and meta in the extern prelude. 2018-09-10 19:41:30 +03:00
Introduce built-in macros through libcore 2019-06-20 11:52:31 +03:00			`error: aborting due to previous error`
rustc_resolve: always include core, std and meta in the extern prelude. 2018-09-10 19:41:30 +03:00
			For more information about this error, try `rustc --explain E0432`.