Lib.rs

› Rust patterns
#backward #guarantees #compatibility #stable #staged #friends #offers

maybe-uninit

MaybeUninit for friends of backwards compatibility

by est31, The Rust Project Developers

2 stable releases

Uses old Rust 2015

2.0.0 Jul 10, 2019
1.0.0 Jul 9, 2019

#1245 in Rust patterns

Download history 107180/week @ 2024-07-22 103645/week @ 2024-07-29 105492/week @ 2024-08-05 121236/week @ 2024-08-12 100451/week @ 2024-08-19 114301/week @ 2024-08-26 94762/week @ 2024-09-02 105116/week @ 2024-09-09 87700/week @ 2024-09-16 106307/week @ 2024-09-23 114183/week @ 2024-09-30 97264/week @ 2024-10-07 115842/week @ 2024-10-14 101928/week @ 2024-10-21 86047/week @ 2024-10-28 84793/week @ 2024-11-04

393,070 downloads per month
Used in 3,662 crates (2 directly)

Apache-2.0 OR MIT

26KB
94 lines

maybe-uninit

Quite often, uses of std::mem::uninitialized() end up in unsound code. Therefore, the MaybeUninit union has been added to std::mem and std::mem::uninitialized() is being deprecated. However, MaybeUninit has been added quite recently. Sometimes you might want to support older versions of Rust as well. Here is where maybe-uninit comes in: it supports stable Rust versions starting with 1.20.0.

Sadly, a feature-complete implementation of MaybeUninit is not possible on stable Rust. Therefore, the library offers the guarantees of MaybeUninit in a staged fashion:

  • Rust 1.36.0 onward: MaybeUninit implementation of Rust stable is being re-exported

  • Rust 1.22.x - 1.35.0: No panicing on uninhabited types, unsoundness when used with types like bool or enums. However, there is protection from accidentially Droping e.g. during unwind!

  • Rust 1.20.x - 1.21.x: No support for Copy/Clone of MaybeUninit<T>, even if T impls Copy or even Clone.

No runtime deps