rust/src/test/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`

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 11:41:30 -05:00			error[E0432]: unresolved import `alloc`
Avoid "whitelist" Other terms are more inclusive and precise. 2020-07-07 10:12:44 -05:00			`--> $DIR/not-allowed.rs:5:5`
rustc_resolve: always include core, std and meta in the extern prelude. 2018-09-10 11:41:30 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| use alloc;`
Improve wording for external crate resolution error I think it reads better this way. 2020-09-30 17:52:13 -05:00			\| ^^^^^ no external crate `alloc`
rustc_resolve: always include core, std and meta in the extern prelude. 2018-09-10 11:41:30 -05:00
Introduce built-in macros through libcore 2019-06-20 03:52:31 -05:00			`error: aborting due to previous error`
rustc_resolve: always include core, std and meta in the extern prelude. 2018-09-10 11:41:30 -05:00
			For more information about this error, try `rustc --explain E0432`.