rust/tests/ui/proc-macro/expand-to-unstable.stderr

error[E0658]: use of unstable library feature 'core_intrinsics': intrinsics are unlikely to ever be stabilized, instead they should be used through stabilized interfaces in the rest of the standard library
  --> $DIR/expand-to-unstable.rs:8:10
   |
LL | #[derive(Unstable)]
   |          ^^^^^^^^
   |
   = help: add `#![feature(core_intrinsics)]` to the crate attributes to enable
   = note: this error originates in the derive macro `Unstable` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
Move former compile-fail-fulldeps tests to ui 2018-12-02 22:27:37 +03:00			`error[E0658]: use of unstable library feature 'core_intrinsics': intrinsics are unlikely to ever be stabilized, instead they should be used through stabilized interfaces in the rest of the standard library`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/expand-to-unstable.rs:8:10`
Move former compile-fail-fulldeps tests to ui 2018-12-02 22:27:37 +03:00			`\|`
			`LL \| #[derive(Unstable)]`
			`\| ^^^^^^^^`
			`\|`
normalize use of backticks in compiler messages for libsyntax/feature_gate https://github.com/rust-lang/rust/issues/60532 2019-07-09 11:32:08 +02:00			= help: add `#![feature(core_intrinsics)]` to the crate attributes to enable
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 14:52:25 -05:00			= note: this error originates in the derive macro `Unstable` (in Nightly builds, run with -Z macro-backtrace for more info)
Move former compile-fail-fulldeps tests to ui 2018-12-02 22:27:37 +03:00
			`error: aborting due to previous error`

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