From 2dd925d34d5e9d36fc8abf21eb97a7500fbfddd3 Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Mon, 1 Oct 2018 10:37:55 +0200 Subject: [PATCH] Don't mention the deprecated panic_implementation It existed only for a very short time, so I think that not many people will remember this attribute. --- .../posts/01-freestanding-rust-binary/index.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/blog/content/second-edition/posts/01-freestanding-rust-binary/index.md b/blog/content/second-edition/posts/01-freestanding-rust-binary/index.md index 7dd231ff..35a6992c 100644 --- a/blog/content/second-edition/posts/01-freestanding-rust-binary/index.md +++ b/blog/content/second-edition/posts/01-freestanding-rust-binary/index.md @@ -134,11 +134,7 @@ This sets the panic strategy to `abort` for both the `dev` profile (used for `ca ### Panic Implementation -The `panic_impl` language item defines the function that the compiler should invoke when a [panic] occurs. Instead of providing the language item directly, we can use the [`panic_handler`] attribute to create a `panic` function. This used to take the for [`panic_implementation`], which has been deprecated and replaced by [`panic_handler`]. - -[`panic_implementation`]: https://github.com/rust-lang/rfcs/blob/master/text/2070-panic-implementation.md#panic_implementation - -Note: [`panic_implementation`] has been deprecated, and we now use [`panic_handler`] instead +The `panic_impl` language item defines the function that the compiler should invoke when a [panic] occurs. Instead of providing the language item directly, we can use the [`panic_handler`] attribute to create a `panic` function. ```rust // in main.rs