about summary refs log tree commit diff
path: root/library/std/src/alloc.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-07-24 23:20:05 +0000
committerbors <bors@rust-lang.org>2023-07-24 23:20:05 +0000
commit1821920cc8e7dc44b0035da890170bf3eadc2ae9 (patch)
tree013a45ab27c69481a14faf521e2ae07ec17b818e /library/std/src/alloc.rs
parent31395ec38250b60b380fd3c27e94756aba3557de (diff)
parentdb4a1534402a163f9296347d31796f070ae7c4e1 (diff)
downloadrust-1821920cc8e7dc44b0035da890170bf3eadc2ae9.tar.gz
rust-1821920cc8e7dc44b0035da890170bf3eadc2ae9.zip
Auto merge of #111362 - mj10021:issue-74838-update, r=cuviper
delete [allow(unused_unsafe)] from issue #74838

While looking into issue #111288 I noticed the following `#[allow(...)]` with a `FIXME` asking for it to be removed.  Deleting the `#[allow(...)]` does not seem to break anything, it seems like the lint has been updated for unsafe blocks in macros?
Diffstat (limited to 'library/std/src/alloc.rs')
-rw-r--r--library/std/src/alloc.rs1
1 files changed, 0 insertions, 1 deletions
diff --git a/library/std/src/alloc.rs b/library/std/src/alloc.rs
index ec774e62deb..1eae7fa6a95 100644
--- a/library/std/src/alloc.rs
+++ b/library/std/src/alloc.rs
@@ -336,7 +336,6 @@ fn default_alloc_error_hook(layout: Layout) {
         static __rust_alloc_error_handler_should_panic: u8;
     }
 
-    #[allow(unused_unsafe)]
     if unsafe { __rust_alloc_error_handler_should_panic != 0 } {
         panic!("memory allocation of {} bytes failed", layout.size());
     } else {