diff options
| author | Ralf Jung <post@ralfj.de> | 2020-09-12 10:43:17 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-09-12 10:43:17 +0200 |
| commit | c20356e96b706f8bc480d905abf218163dc9ff30 (patch) | |
| tree | a094ed1eb70fe1b1db19cc72b8fe3c010a91add0 /compiler/rustc_codegen_llvm/src | |
| parent | 5d90d6ee903d547cbb708b059c3b18b81fb7827c (diff) | |
| parent | 43c7a9b72b284bee6ce8517550cb6ee7903c639e (diff) | |
| download | rust-c20356e96b706f8bc480d905abf218163dc9ff30.tar.gz rust-c20356e96b706f8bc480d905abf218163dc9ff30.zip | |
Rollup merge of #76484 - fusion-engineering-forks:maybe-uninit-drop, r=RalfJung
Add MaybeUninit::assume_init_drop. `ManuallyDrop`'s documentation tells the user to use `MaybeUninit` instead when handling uninitialized data. However, the main functionality of `ManuallyDrop` (`drop`) is not available directly on `MaybeUninit`. Adding it makes it easier to switch from one to the other. I re-used the `maybe_uninit_extra` feature and tracking issue number (#63567), since it seems very related. (And to avoid creating too many features tracking issues for `MaybeUninit`.)
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions