[PATCH v1 proxmox 4/6] io: remove boxed::uninitialized because it is unsound

[Robert Obkircher <r.obkircher@proxmox.com>]

Using this function could result in miscompilations, and it was also
missing a null check. Remove it, since it appears to be unused.

Signed-off-by: Robert Obkircher <r.obkircher@proxmox.com>
---
 proxmox-io/src/boxed.rs | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/proxmox-io/src/boxed.rs b/proxmox-io/src/boxed.rs
index fb67bfd7..abd60a1f 100644
--- a/proxmox-io/src/boxed.rs
+++ b/proxmox-io/src/boxed.rs
@@ -1,15 +1,3 @@
-/// Uninitialized bytes, without `MaybeUninit`.
-///
-/// We're talking about bytes here, which we *allocate*. That is, we call a function, get a pointer
-/// to stuff, and can use it. It's not UB in that there's nothing undefined about what's going on
-/// here.
-pub fn uninitialized(len: usize) -> Box<[u8]> {
-    unsafe {
-        let data = std::alloc::alloc(std::alloc::Layout::array::<u8>(len).unwrap());
-        Box::from_raw(std::ptr::slice_from_raw_parts_mut(data, len))
-    }
-}
-
 /// Zero-initialized bytes, meant for large sizes to avoid busting the stack.
 pub fn zeroed(len: usize) -> Box<[u8]> {
     // vec! guarantees not to over-allocate, so shrink_to_fit inside into_boxed_slice does nothing
-- 
2.47.3