about summary refs log tree commit diff
path: root/src/libcore/mem.rs
AgeCommit message (Collapse)AuthorLines
2019-05-29split libcore::mem into multiple filesRalf Jung-1406/+0
2019-05-28Update src/libcore/mem.rsRalf Jung-1/+1
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
2019-05-28mention that MaybeUninit is a bit like OptionRalf Jung-0/+3
2019-05-25MaybeUninit doctest: remove unnecessary type ascriptionRalf Jung-2/+2
2019-05-21adjust deprecation date of mem::uninitializedRalf Jung-1/+1
2019-05-20Document layout guarantee of MaybeUninitPeter Todd-0/+22
2019-05-20elliminate mem::uninitialize from docs in libcoreRalf Jung-56/+0
2019-05-20add out-pointer exampleRalf Jung-1/+25
2019-05-20apply feedbackRalf Jung-28/+36
2019-05-20stabilize core parts of MaybeUninit and deprecate mem::uninitialized in the ↵Ralf Jung-165/+135
future Also expand the documentation a bit
2019-05-07Rollup merge of #60609 - spastorino:be-explicit-on-mem-replace-doc, r=CentrilMazdak Farrokhzad-2/+2
Be a bit more explicit asserting over the vec rather than the len
2019-05-07Be a bit more explicit asserting over the vec rather than the lenSantiago Pastorino-2/+2
2019-04-29const-stabilize std::mem::needs_dropYuki OKUSHI-1/+0
2019-04-19libcore: deny more...Mazdak Farrokhzad-1/+1
2019-04-18libcore => 2018Taiki Endo-9/+9
2019-04-12MaybeUninit: remove deprecated functionsRalf Jung-34/+0
2019-03-26adjust MaybeUninit API to discussionsRalf Jung-38/+72
uninitialized -> uninit into_initialized -> assume_init read_initialized -> read set -> write
2019-03-11Improvements to comments in libstd, libcore, liballoc.Alexander Regueiro-3/+6
2019-03-09Rollup merge of #58660 - RalfJung:maybe-uninit, r=CentrilMazdak Farrokhzad-29/+224
MaybeUninit: add read_initialized, add examples This adds a new `read_initialized` method, similar to suggestions by @Amanieu and @shepmaster. I also added examples to this and other methods.
2019-03-06Apply suggestions from code reviewRalf Jung-1/+1
2019-03-06Apply suggestions from code reviewMazdak Farrokhzad-3/+3
Co-Authored-By: RalfJung <post@ralfj.de>
2019-02-28Update src/libcore/mem.rsMazdak Farrokhzad-1/+1
Co-Authored-By: RalfJung <post@ralfj.de>
2019-02-27improve readabilityRalf Jung-1/+1
2019-02-27ManuallyDrop != MaybeUninitRalf Jung-0/+8
2019-02-25heading # Unsafety => # Safety in stdlib docs.Mazdak Farrokhzad-3/+3
2019-02-24prefer into_initialized over read_initialitedRalf Jung-0/+3
2019-02-24show how to set with ptr::writeRalf Jung-4/+5
2019-02-24remark that the rules are unfinishedRalf Jung-0/+4
2019-02-23fix linkRalf Jung-0/+2
2019-02-23expand type nameRalf Jung-17/+17
2019-02-23Apply suggestions from code reviewMazdak Farrokhzad-18/+19
Co-Authored-By: RalfJung <post@ralfj.de>
2019-02-22make MaybeUninit CopyRalf Jung-0/+10
2019-02-22examples for MaybeUninit::zeroedRalf Jung-0/+29
2019-02-22examples for as[_mut]_ptrRalf Jung-0/+53
2019-02-22misc tweaksRalf Jung-12/+22
2019-02-22also add examples to MaybeUninit::into_initializedRalf Jung-1/+28
2019-02-22Add MaybeUninit::read_uninitializedRalf Jung-0/+55
Also remove a no-longer accurate comments
2019-02-18Auto merge of #58373 - RalfJung:maybe-uninit, r=gnzlbgbors-8/+0
update stdsimd and remove now-unused MaybeUninit::into_inner That's a huge diff for stdsimd... Cc @gnzlbg @alexcrichton
2019-02-16Rollup merge of #58468 - RalfJung:maybe-uninit-split, r=Centrilkennytm-27/+49
split MaybeUninit into several features, expand docs a bit This splits the `maybe_uninit` feature gate into several: * `maybe_uninit` for what we will hopefully stabilize soon-ish. * `maybe_uninit_ref` for creating references into `MaybeUninit`, for which the rules are not yet clear. * `maybe_uninit_slice` for handling slices of `MaybeUninit`, which needs more API design work. * `maybe_uninit_array` for creating arrays of `MaybeUninit` using a macro (because we don't have https://github.com/rust-lang/rust/issues/49147 yet). Is that an okay thing to do? The goal is to help people avoid APIs we do not want to stabilize yet. I used this to make sure rustc itself does not use `get_ref` and `get_mut`. I also extended the docs to advise against uninitialized integers -- again this is something for which the rules are still being discussed.
2019-02-14split MaybeUninit into several features, expand docs a bitRalf Jung-27/+49
2019-02-14remove MaybeUninit::into_innerRalf Jung-8/+0
2019-02-14Rollup merge of #57856 - lzutao:fix-old-first-edition, r=steveklabnikMazdak Farrokhzad-1/+1
Convert old first edition links to current edition one r? @steveklabnik
2019-02-13Convert old doc links to current editionLzu Tao-1/+1
Use footnote style to bypass the tidy check
2019-02-10libs: doc commentsAlexander Regueiro-20/+24
2019-02-10tests: doc commentsAlexander Regueiro-2/+2
2019-02-10Auto merge of #58129 - RalfJung:maybe-uninit, r=cramertjbors-7/+53
MaybeUninit: some docs, rename into_inner -> into_initialized, return &mut from set
2019-02-10it is okay not to use into_innerRalf Jung-0/+1
2019-02-07Rollup merge of #57848 - jrvanwhy:transmute-export-doc, r=QuietMisdreavusGuillaume Gomez-0/+1
Generate a documentation page for core::mem::transmute. In `#[no_std]` environments, `std::mem::transmute` is unavailable. Searching for "core transmute" online only pulls up `core::intrinsics::transmute`, which is behind the (unstable) `core_intrinsics` feature flag. Users wishing to use transmute in `#[no_std]` environments typically should use `core::mem::transmute` instead, as it is stable. This documentation makes `core::mem::transmute` discoverable.
2019-02-06fix doctestsRalf Jung-1/+2
2019-02-05fix doctestRalf Jung-2/+2
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-25 08:56:33 +0000