mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-22 23:04:33 +00:00
Improve docs for mem::forget()
We were burying the reason to use this function below a bunch of caveats about its usage. That's backwards. Why a function should be used belongs at the top of the docs, not the bottom. Also, add some extra links to related functions mentioned in the body.
This commit is contained in:
parent
c980aba9a8
commit
5af1b3f3a3
@ -29,6 +29,19 @@ pub use intrinsics::transmute;
|
|||||||
/// `mem::drop` function in that it **does not run the destructor**, leaking the
|
/// `mem::drop` function in that it **does not run the destructor**, leaking the
|
||||||
/// value and any resources that it owns.
|
/// value and any resources that it owns.
|
||||||
///
|
///
|
||||||
|
/// There's only a few reasons to use this function. They mainly come
|
||||||
|
/// up in unsafe code or FFI code.
|
||||||
|
///
|
||||||
|
/// * You have an uninitialized value, perhaps for performance reasons, and
|
||||||
|
/// need to prevent the destructor from running on it.
|
||||||
|
/// * You have two copies of a value (like when writing something like
|
||||||
|
/// [`mem::swap`][swap]), but need the destructor to only run once to
|
||||||
|
/// prevent a double `free`.
|
||||||
|
/// * Transferring resources across [FFI][ffi] boundries.
|
||||||
|
///
|
||||||
|
/// [swap]: fn.swap.html
|
||||||
|
/// [ffi]: ../../book/ffi.html
|
||||||
|
///
|
||||||
/// # Safety
|
/// # Safety
|
||||||
///
|
///
|
||||||
/// This function is not marked as `unsafe` as Rust does not guarantee that the
|
/// This function is not marked as `unsafe` as Rust does not guarantee that the
|
||||||
@ -52,20 +65,9 @@ pub use intrinsics::transmute;
|
|||||||
/// * `mpsc::{Sender, Receiver}` cycles (they use `Arc` internally)
|
/// * `mpsc::{Sender, Receiver}` cycles (they use `Arc` internally)
|
||||||
/// * Panicking destructors are likely to leak local resources
|
/// * Panicking destructors are likely to leak local resources
|
||||||
///
|
///
|
||||||
/// # When To Use
|
|
||||||
///
|
|
||||||
/// There's only a few reasons to use this function. They mainly come
|
|
||||||
/// up in unsafe code or FFI code.
|
|
||||||
///
|
|
||||||
/// * You have an uninitialized value, perhaps for performance reasons, and
|
|
||||||
/// need to prevent the destructor from running on it.
|
|
||||||
/// * You have two copies of a value (like `std::mem::swap`), but need the
|
|
||||||
/// destructor to only run once to prevent a double free.
|
|
||||||
/// * Transferring resources across FFI boundries.
|
|
||||||
///
|
|
||||||
/// # Example
|
/// # Example
|
||||||
///
|
///
|
||||||
/// Leak some heap memory by never deallocating it.
|
/// Leak some heap memory by never deallocating it:
|
||||||
///
|
///
|
||||||
/// ```rust
|
/// ```rust
|
||||||
/// use std::mem;
|
/// use std::mem;
|
||||||
@ -74,7 +76,7 @@ pub use intrinsics::transmute;
|
|||||||
/// mem::forget(heap_memory);
|
/// mem::forget(heap_memory);
|
||||||
/// ```
|
/// ```
|
||||||
///
|
///
|
||||||
/// Leak an I/O object, never closing the file.
|
/// Leak an I/O object, never closing the file:
|
||||||
///
|
///
|
||||||
/// ```rust,no_run
|
/// ```rust,no_run
|
||||||
/// use std::mem;
|
/// use std::mem;
|
||||||
@ -84,7 +86,7 @@ pub use intrinsics::transmute;
|
|||||||
/// mem::forget(file);
|
/// mem::forget(file);
|
||||||
/// ```
|
/// ```
|
||||||
///
|
///
|
||||||
/// The swap function uses forget to good effect.
|
/// The `mem::swap` function uses `mem::forget` to good effect:
|
||||||
///
|
///
|
||||||
/// ```rust
|
/// ```rust
|
||||||
/// use std::mem;
|
/// use std::mem;
|
||||||
|
Loading…
Reference in New Issue
Block a user