about summary refs log tree commit diff
path: root/library/alloc/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/alloc/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/alloc/src/alloc.rs')
-rw-r--r--library/alloc/src/alloc.rs1
1 files changed, 0 insertions, 1 deletions
diff --git a/library/alloc/src/alloc.rs b/library/alloc/src/alloc.rs
index c8751ba4911..5205ed9fb50 100644
--- a/library/alloc/src/alloc.rs
+++ b/library/alloc/src/alloc.rs
@@ -392,7 +392,6 @@ pub mod __alloc_error_handler {
             static __rust_alloc_error_handler_should_panic: u8;
         }
 
-        #[allow(unused_unsafe)]
         if unsafe { __rust_alloc_error_handler_should_panic != 0 } {
             panic!("memory allocation of {size} bytes failed")
         } else {