#backward #compatibility #stable #guarantees #staged #friends #offers

maybe-uninit

MaybeUninit for friends of backwards compatibility

2 stable releases

Uses old Rust 2015

2.0.0 Jul 10, 2019
1.0.0 Jul 9, 2019

#1101 in Rust patterns

Download history 106906/week @ 2024-06-19 106300/week @ 2024-06-26 101130/week @ 2024-07-03 112793/week @ 2024-07-10 104254/week @ 2024-07-17 105923/week @ 2024-07-24 102779/week @ 2024-07-31 125195/week @ 2024-08-07 99292/week @ 2024-08-14 107938/week @ 2024-08-21 94312/week @ 2024-08-28 111352/week @ 2024-09-04 96097/week @ 2024-09-11 95291/week @ 2024-09-18 109055/week @ 2024-09-25 90270/week @ 2024-10-02

412,760 downloads per month
Used in 3,663 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