Lib.rs

› Rust patterns
#backward #compatibility #stable #friends #guarantees #bool #copy-clone

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

#866 in Rust patterns

Download history 87201/week @ 2024-01-05 79212/week @ 2024-01-12 101336/week @ 2024-01-19 104722/week @ 2024-01-26 110060/week @ 2024-02-02 114643/week @ 2024-02-09 99939/week @ 2024-02-16 124470/week @ 2024-02-23 123242/week @ 2024-03-01 113618/week @ 2024-03-08 118231/week @ 2024-03-15 109655/week @ 2024-03-22 127299/week @ 2024-03-29 101183/week @ 2024-04-05 104151/week @ 2024-04-12 91476/week @ 2024-04-19

447,723 downloads per month
Used in 3,694 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