rust/src/test/ui/feature-gates/feature-gate-alloc-error-handler.rs

// compile-flags:-C panic=abort

#![no_std]
#![no_main]

use core::alloc::Layout;

#[alloc_error_handler] //~ ERROR `#[alloc_error_handler]` is an unstable feature
fn oom(info: Layout) -> ! {
    loop {}
}

#[panic_handler]
fn panic(_: &core::panic::PanicInfo) -> ! { loop {} }
Implement #[alloc_error_handler] This to-be-stable attribute is equivalent to `#[lang = "oom"]`. It is required when using the alloc crate without the std crate. It is called by `handle_alloc_error`, which is in turned called by "infallible" allocations APIs such as `Vec::push`. 2018-07-06 15:49:52 +02:00			`// compile-flags:-C panic=abort`

			`#![no_std]`
			`#![no_main]`

			`use core::alloc::Layout;`

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			#[alloc_error_handler] //~ ERROR `#[alloc_error_handler]` is an unstable feature
Implement #[alloc_error_handler] This to-be-stable attribute is equivalent to `#[lang = "oom"]`. It is required when using the alloc crate without the std crate. It is called by `handle_alloc_error`, which is in turned called by "infallible" allocations APIs such as `Vec::push`. 2018-07-06 15:49:52 +02:00			`fn oom(info: Layout) -> ! {`
			`loop {}`
			`}`
Make sure feature gate errors are recoverable (take 2) 2019-01-02 17:14:24 +03:00
			`#[panic_handler]`
			`fn panic(_: &core::panic::PanicInfo) -> ! { loop {} }`