rustc/vendor/maybe-uninit
2020-08-06 23:19:31 +01:00
..
src New upstream version 1.46.0~beta.2+dfsg1 2020-08-06 23:19:31 +01:00
tests New upstream version 1.46.0~beta.2+dfsg1 2020-08-06 23:19:31 +01:00
.cargo-checksum.json New upstream version 1.46.0~beta.2+dfsg1 2020-08-06 23:19:31 +01:00
build.rs New upstream version 1.46.0~beta.2+dfsg1 2020-08-06 23:19:31 +01:00
Cargo.toml New upstream version 1.46.0~beta.2+dfsg1 2020-08-06 23:19:31 +01:00
LICENSE-APACHE New upstream version 1.46.0~beta.2+dfsg1 2020-08-06 23:19:31 +01:00
LICENSE-MIT New upstream version 1.46.0~beta.2+dfsg1 2020-08-06 23:19:31 +01:00
README.md New upstream version 1.46.0~beta.2+dfsg1 2020-08-06 23:19:31 +01:00

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.