2014-02-18 20:30:21 +00:00
|
|
|
// Copyright 2012-2014 The Rust Project Developers. See the COPYRIGHT
|
2013-10-16 18:34:01 -07:00
|
|
|
// file at the top-level directory of this distribution and at
|
|
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
|
|
// option. This file may not be copied, modified, or distributed
|
|
|
|
// except according to those terms.
|
|
|
|
|
2014-02-09 00:23:04 -08:00
|
|
|
//! Basic functions for dealing with memory
|
|
|
|
//!
|
|
|
|
//! This module contains functions for querying the size and alignment of
|
|
|
|
//! types, initializing and manipulating memory.
|
2013-10-16 18:34:01 -07:00
|
|
|
|
2014-02-15 23:49:08 -08:00
|
|
|
use intrinsics;
|
2014-06-16 11:25:47 -07:00
|
|
|
use ptr;
|
2013-10-16 18:34:01 -07:00
|
|
|
|
2014-06-12 14:08:44 -07:00
|
|
|
pub use intrinsics::transmute;
|
|
|
|
|
2014-08-14 02:15:09 -04:00
|
|
|
/// Moves a thing into the void.
|
|
|
|
///
|
|
|
|
/// The forget function will take ownership of the provided value but neglect
|
|
|
|
/// to run any required cleanup or memory management operations on it.
|
|
|
|
///
|
|
|
|
/// This function is the unsafe version of the `drop` function because it does
|
|
|
|
/// not run any destructors.
|
|
|
|
#[stable]
|
|
|
|
pub use intrinsics::forget;
|
|
|
|
|
2014-02-18 20:30:21 +00:00
|
|
|
/// Returns the size of a type in bytes.
|
2013-10-16 18:34:01 -07:00
|
|
|
#[inline]
|
2014-05-17 00:56:00 -07:00
|
|
|
#[stable]
|
2013-10-16 18:34:01 -07:00
|
|
|
pub fn size_of<T>() -> uint {
|
|
|
|
unsafe { intrinsics::size_of::<T>() }
|
|
|
|
}
|
|
|
|
|
2014-02-18 20:30:21 +00:00
|
|
|
/// Returns the size of the type that `_val` points to in bytes.
|
2013-10-16 18:34:01 -07:00
|
|
|
#[inline]
|
2014-05-23 20:53:56 -07:00
|
|
|
#[stable]
|
2013-10-16 18:34:01 -07:00
|
|
|
pub fn size_of_val<T>(_val: &T) -> uint {
|
|
|
|
size_of::<T>()
|
|
|
|
}
|
|
|
|
|
2013-10-21 21:41:32 +02:00
|
|
|
/// Returns the ABI-required minimum alignment of a type
|
|
|
|
///
|
|
|
|
/// This is the alignment used for struct fields. It may be smaller
|
|
|
|
/// than the preferred alignment.
|
2013-10-16 18:34:01 -07:00
|
|
|
#[inline]
|
2014-05-17 00:56:00 -07:00
|
|
|
#[stable]
|
2013-10-16 18:34:01 -07:00
|
|
|
pub fn min_align_of<T>() -> uint {
|
|
|
|
unsafe { intrinsics::min_align_of::<T>() }
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Returns the ABI-required minimum alignment of the type of the value that
|
|
|
|
/// `_val` points to
|
|
|
|
#[inline]
|
2014-05-23 20:53:56 -07:00
|
|
|
#[stable]
|
2013-10-16 18:34:01 -07:00
|
|
|
pub fn min_align_of_val<T>(_val: &T) -> uint {
|
|
|
|
min_align_of::<T>()
|
|
|
|
}
|
|
|
|
|
2014-05-17 00:56:00 -07:00
|
|
|
/// Returns the alignment in memory for a type.
|
|
|
|
///
|
|
|
|
/// This function will return the alignment, in bytes, of a type in memory. If
|
|
|
|
/// the alignment returned is adhered to, then the type is guaranteed to
|
|
|
|
/// function properly.
|
2013-10-16 18:34:01 -07:00
|
|
|
#[inline]
|
2014-05-17 00:56:00 -07:00
|
|
|
#[stable]
|
|
|
|
pub fn align_of<T>() -> uint {
|
|
|
|
// We use the preferred alignment as the default alignment for a type. This
|
|
|
|
// appears to be what clang migrated towards as well:
|
|
|
|
//
|
|
|
|
// http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20110725/044411.html
|
2013-10-16 18:34:01 -07:00
|
|
|
unsafe { intrinsics::pref_align_of::<T>() }
|
|
|
|
}
|
|
|
|
|
2014-05-17 00:56:00 -07:00
|
|
|
/// Returns the alignment of the type of the value that `_val` points to.
|
|
|
|
///
|
|
|
|
/// This is similar to `align_of`, but function will properly handle types such
|
|
|
|
/// as trait objects (in the future), returning the alignment for an arbitrary
|
|
|
|
/// value at runtime.
|
2013-10-16 18:34:01 -07:00
|
|
|
#[inline]
|
2014-05-23 20:53:56 -07:00
|
|
|
#[stable]
|
2014-05-17 00:56:00 -07:00
|
|
|
pub fn align_of_val<T>(_val: &T) -> uint {
|
|
|
|
align_of::<T>()
|
2013-10-16 18:34:01 -07:00
|
|
|
}
|
|
|
|
|
2014-02-08 02:46:55 -08:00
|
|
|
/// Create a value initialized to zero.
|
|
|
|
///
|
2014-11-16 16:51:22 -08:00
|
|
|
/// This function is similar to allocating space for a local variable and
|
2014-05-17 00:56:00 -07:00
|
|
|
/// zeroing it out (an unsafe operation).
|
|
|
|
///
|
|
|
|
/// Care must be taken when using this function, if the type `T` has a
|
|
|
|
/// destructor and the value falls out of scope (due to unwinding or returning)
|
|
|
|
/// before being initialized, then the destructor will run on zeroed
|
|
|
|
/// data, likely leading to crashes.
|
|
|
|
///
|
|
|
|
/// This is useful for FFI functions sometimes, but should generally be avoided.
|
2014-02-08 02:46:55 -08:00
|
|
|
#[inline]
|
2014-05-23 20:53:56 -07:00
|
|
|
#[stable]
|
2014-05-17 00:56:00 -07:00
|
|
|
pub unsafe fn zeroed<T>() -> T {
|
2014-02-08 02:46:55 -08:00
|
|
|
intrinsics::init()
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Create an uninitialized value.
|
2014-05-17 00:56:00 -07:00
|
|
|
///
|
|
|
|
/// Care must be taken when using this function, if the type `T` has a
|
|
|
|
/// destructor and the value falls out of scope (due to unwinding or returning)
|
|
|
|
/// before being initialized, then the destructor will run on uninitialized
|
|
|
|
/// data, likely leading to crashes.
|
|
|
|
///
|
|
|
|
/// This is useful for FFI functions sometimes, but should generally be avoided.
|
2014-02-08 02:46:55 -08:00
|
|
|
#[inline]
|
2014-05-23 20:53:56 -07:00
|
|
|
#[stable]
|
|
|
|
pub unsafe fn uninitialized<T>() -> T {
|
|
|
|
intrinsics::uninit()
|
|
|
|
}
|
|
|
|
|
2014-06-16 00:22:51 -07:00
|
|
|
/// Swap the values at two mutable locations of the same type, without
|
|
|
|
/// deinitialising or copying either one.
|
2014-02-01 04:35:36 +08:00
|
|
|
#[inline]
|
2014-05-17 00:56:00 -07:00
|
|
|
#[stable]
|
2014-02-01 04:35:36 +08:00
|
|
|
pub fn swap<T>(x: &mut T, y: &mut T) {
|
|
|
|
unsafe {
|
|
|
|
// Give ourselves some scratch space to work with
|
2014-05-23 20:53:56 -07:00
|
|
|
let mut t: T = uninitialized();
|
2014-02-01 04:35:36 +08:00
|
|
|
|
|
|
|
// Perform the swap, `&mut` pointers never alias
|
|
|
|
ptr::copy_nonoverlapping_memory(&mut t, &*x, 1);
|
|
|
|
ptr::copy_nonoverlapping_memory(x, &*y, 1);
|
|
|
|
ptr::copy_nonoverlapping_memory(y, &t, 1);
|
|
|
|
|
2014-04-16 10:53:09 +02:00
|
|
|
// y and t now point to the same thing, but we need to completely forget `t`
|
2014-02-01 04:35:36 +08:00
|
|
|
// because it's no longer relevant.
|
core: Remove the cast module
This commit revisits the `cast` module in libcore and libstd, and scrutinizes
all functions inside of it. The result was to remove the `cast` module entirely,
folding all functionality into the `mem` module. Specifically, this is the fate
of each function in the `cast` module.
* transmute - This function was moved to `mem`, but it is now marked as
#[unstable]. This is due to planned changes to the `transmute`
function and how it can be invoked (see the #[unstable] comment).
For more information, see RFC 5 and #12898
* transmute_copy - This function was moved to `mem`, with clarification that is
is not an error to invoke it with T/U that are different
sizes, but rather that it is strongly discouraged. This
function is now #[stable]
* forget - This function was moved to `mem` and marked #[stable]
* bump_box_refcount - This function was removed due to the deprecation of
managed boxes as well as its questionable utility.
* transmute_mut - This function was previously deprecated, and removed as part
of this commit.
* transmute_mut_unsafe - This function doesn't serve much of a purpose when it
can be achieved with an `as` in safe code, so it was
removed.
* transmute_lifetime - This function was removed because it is likely a strong
indication that code is incorrect in the first place.
* transmute_mut_lifetime - This function was removed for the same reasons as
`transmute_lifetime`
* copy_lifetime - This function was moved to `mem`, but it is marked
`#[unstable]` now due to the likelihood of being removed in
the future if it is found to not be very useful.
* copy_mut_lifetime - This function was also moved to `mem`, but had the same
treatment as `copy_lifetime`.
* copy_lifetime_vec - This function was removed because it is not used today,
and its existence is not necessary with DST
(copy_lifetime will suffice).
In summary, the cast module was stripped down to these functions, and then the
functions were moved to the `mem` module.
transmute - #[unstable]
transmute_copy - #[stable]
forget - #[stable]
copy_lifetime - #[unstable]
copy_mut_lifetime - #[unstable]
[breaking-change]
2014-05-09 10:34:51 -07:00
|
|
|
forget(t);
|
2014-02-01 04:35:36 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-06-16 00:22:51 -07:00
|
|
|
/// Replace the value at a mutable location with a new one, returning the old
|
|
|
|
/// value, without deinitialising or copying either one.
|
|
|
|
///
|
|
|
|
/// This is primarily used for transferring and swapping ownership of a value
|
|
|
|
/// in a mutable location. For example, this function allows consumption of
|
|
|
|
/// one field of a struct by replacing it with another value. The normal approach
|
|
|
|
/// doesn't always work:
|
|
|
|
///
|
|
|
|
/// ```rust,ignore
|
|
|
|
/// struct Buffer<T> { buf: Vec<T> }
|
|
|
|
///
|
|
|
|
/// impl<T> Buffer<T> {
|
|
|
|
/// fn get_and_reset(&mut self) -> Vec<T> {
|
|
|
|
/// // error: cannot move out of dereference of `&mut`-pointer
|
|
|
|
/// let buf = self.buf;
|
|
|
|
/// self.buf = Vec::new();
|
|
|
|
/// buf
|
|
|
|
/// }
|
|
|
|
/// }
|
|
|
|
/// ```
|
|
|
|
///
|
|
|
|
/// Note that `T` does not necessarily implement `Clone`, so it can't even
|
|
|
|
/// clone and reset `self.buf`. But `replace` can be used to disassociate
|
|
|
|
/// the original value of `self.buf` from `self`, allowing it to be returned:
|
|
|
|
///
|
|
|
|
/// ```rust
|
|
|
|
/// # struct Buffer<T> { buf: Vec<T> }
|
|
|
|
/// impl<T> Buffer<T> {
|
|
|
|
/// fn get_and_reset(&mut self) -> Vec<T> {
|
|
|
|
/// use std::mem::replace;
|
|
|
|
/// replace(&mut self.buf, Vec::new())
|
|
|
|
/// }
|
|
|
|
/// }
|
|
|
|
/// ```
|
2014-02-01 04:35:36 +08:00
|
|
|
#[inline]
|
2014-05-17 00:56:00 -07:00
|
|
|
#[stable]
|
2014-02-01 04:35:36 +08:00
|
|
|
pub fn replace<T>(dest: &mut T, mut src: T) -> T {
|
|
|
|
swap(dest, &mut src);
|
|
|
|
src
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Disposes of a value.
|
core: Remove the cast module
This commit revisits the `cast` module in libcore and libstd, and scrutinizes
all functions inside of it. The result was to remove the `cast` module entirely,
folding all functionality into the `mem` module. Specifically, this is the fate
of each function in the `cast` module.
* transmute - This function was moved to `mem`, but it is now marked as
#[unstable]. This is due to planned changes to the `transmute`
function and how it can be invoked (see the #[unstable] comment).
For more information, see RFC 5 and #12898
* transmute_copy - This function was moved to `mem`, with clarification that is
is not an error to invoke it with T/U that are different
sizes, but rather that it is strongly discouraged. This
function is now #[stable]
* forget - This function was moved to `mem` and marked #[stable]
* bump_box_refcount - This function was removed due to the deprecation of
managed boxes as well as its questionable utility.
* transmute_mut - This function was previously deprecated, and removed as part
of this commit.
* transmute_mut_unsafe - This function doesn't serve much of a purpose when it
can be achieved with an `as` in safe code, so it was
removed.
* transmute_lifetime - This function was removed because it is likely a strong
indication that code is incorrect in the first place.
* transmute_mut_lifetime - This function was removed for the same reasons as
`transmute_lifetime`
* copy_lifetime - This function was moved to `mem`, but it is marked
`#[unstable]` now due to the likelihood of being removed in
the future if it is found to not be very useful.
* copy_mut_lifetime - This function was also moved to `mem`, but had the same
treatment as `copy_lifetime`.
* copy_lifetime_vec - This function was removed because it is not used today,
and its existence is not necessary with DST
(copy_lifetime will suffice).
In summary, the cast module was stripped down to these functions, and then the
functions were moved to the `mem` module.
transmute - #[unstable]
transmute_copy - #[stable]
forget - #[stable]
copy_lifetime - #[unstable]
copy_mut_lifetime - #[unstable]
[breaking-change]
2014-05-09 10:34:51 -07:00
|
|
|
///
|
|
|
|
/// This function can be used to destroy any value by allowing `drop` to take
|
|
|
|
/// ownership of its argument.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
|
|
|
/// use std::cell::RefCell;
|
|
|
|
///
|
2014-04-21 17:58:52 -04:00
|
|
|
/// let x = RefCell::new(1i);
|
core: Remove the cast module
This commit revisits the `cast` module in libcore and libstd, and scrutinizes
all functions inside of it. The result was to remove the `cast` module entirely,
folding all functionality into the `mem` module. Specifically, this is the fate
of each function in the `cast` module.
* transmute - This function was moved to `mem`, but it is now marked as
#[unstable]. This is due to planned changes to the `transmute`
function and how it can be invoked (see the #[unstable] comment).
For more information, see RFC 5 and #12898
* transmute_copy - This function was moved to `mem`, with clarification that is
is not an error to invoke it with T/U that are different
sizes, but rather that it is strongly discouraged. This
function is now #[stable]
* forget - This function was moved to `mem` and marked #[stable]
* bump_box_refcount - This function was removed due to the deprecation of
managed boxes as well as its questionable utility.
* transmute_mut - This function was previously deprecated, and removed as part
of this commit.
* transmute_mut_unsafe - This function doesn't serve much of a purpose when it
can be achieved with an `as` in safe code, so it was
removed.
* transmute_lifetime - This function was removed because it is likely a strong
indication that code is incorrect in the first place.
* transmute_mut_lifetime - This function was removed for the same reasons as
`transmute_lifetime`
* copy_lifetime - This function was moved to `mem`, but it is marked
`#[unstable]` now due to the likelihood of being removed in
the future if it is found to not be very useful.
* copy_mut_lifetime - This function was also moved to `mem`, but had the same
treatment as `copy_lifetime`.
* copy_lifetime_vec - This function was removed because it is not used today,
and its existence is not necessary with DST
(copy_lifetime will suffice).
In summary, the cast module was stripped down to these functions, and then the
functions were moved to the `mem` module.
transmute - #[unstable]
transmute_copy - #[stable]
forget - #[stable]
copy_lifetime - #[unstable]
copy_mut_lifetime - #[unstable]
[breaking-change]
2014-05-09 10:34:51 -07:00
|
|
|
///
|
|
|
|
/// let mut mutable_borrow = x.borrow_mut();
|
|
|
|
/// *mutable_borrow = 1;
|
|
|
|
/// drop(mutable_borrow); // relinquish the mutable borrow on this slot
|
|
|
|
///
|
|
|
|
/// let borrow = x.borrow();
|
|
|
|
/// println!("{}", *borrow);
|
|
|
|
/// ```
|
2014-02-01 04:35:36 +08:00
|
|
|
#[inline]
|
2014-05-17 00:56:00 -07:00
|
|
|
#[stable]
|
2014-02-01 04:35:36 +08:00
|
|
|
pub fn drop<T>(_x: T) { }
|
|
|
|
|
core: Remove the cast module
This commit revisits the `cast` module in libcore and libstd, and scrutinizes
all functions inside of it. The result was to remove the `cast` module entirely,
folding all functionality into the `mem` module. Specifically, this is the fate
of each function in the `cast` module.
* transmute - This function was moved to `mem`, but it is now marked as
#[unstable]. This is due to planned changes to the `transmute`
function and how it can be invoked (see the #[unstable] comment).
For more information, see RFC 5 and #12898
* transmute_copy - This function was moved to `mem`, with clarification that is
is not an error to invoke it with T/U that are different
sizes, but rather that it is strongly discouraged. This
function is now #[stable]
* forget - This function was moved to `mem` and marked #[stable]
* bump_box_refcount - This function was removed due to the deprecation of
managed boxes as well as its questionable utility.
* transmute_mut - This function was previously deprecated, and removed as part
of this commit.
* transmute_mut_unsafe - This function doesn't serve much of a purpose when it
can be achieved with an `as` in safe code, so it was
removed.
* transmute_lifetime - This function was removed because it is likely a strong
indication that code is incorrect in the first place.
* transmute_mut_lifetime - This function was removed for the same reasons as
`transmute_lifetime`
* copy_lifetime - This function was moved to `mem`, but it is marked
`#[unstable]` now due to the likelihood of being removed in
the future if it is found to not be very useful.
* copy_mut_lifetime - This function was also moved to `mem`, but had the same
treatment as `copy_lifetime`.
* copy_lifetime_vec - This function was removed because it is not used today,
and its existence is not necessary with DST
(copy_lifetime will suffice).
In summary, the cast module was stripped down to these functions, and then the
functions were moved to the `mem` module.
transmute - #[unstable]
transmute_copy - #[stable]
forget - #[stable]
copy_lifetime - #[unstable]
copy_mut_lifetime - #[unstable]
[breaking-change]
2014-05-09 10:34:51 -07:00
|
|
|
/// Interprets `src` as `&U`, and then reads `src` without moving the contained
|
|
|
|
/// value.
|
|
|
|
///
|
|
|
|
/// This function will unsafely assume the pointer `src` is valid for
|
|
|
|
/// `sizeof(U)` bytes by transmuting `&T` to `&U` and then reading the `&U`. It
|
|
|
|
/// will also unsafely create a copy of the contained value instead of moving
|
|
|
|
/// out of `src`.
|
|
|
|
///
|
|
|
|
/// It is not a compile-time error if `T` and `U` have different sizes, but it
|
|
|
|
/// is highly encouraged to only invoke this function where `T` and `U` have the
|
|
|
|
/// same size. This function triggers undefined behavior if `U` is larger than
|
|
|
|
/// `T`.
|
|
|
|
#[inline]
|
|
|
|
#[stable]
|
|
|
|
pub unsafe fn transmute_copy<T, U>(src: &T) -> U {
|
2014-06-25 12:47:34 -07:00
|
|
|
ptr::read(src as *const T as *const U)
|
core: Remove the cast module
This commit revisits the `cast` module in libcore and libstd, and scrutinizes
all functions inside of it. The result was to remove the `cast` module entirely,
folding all functionality into the `mem` module. Specifically, this is the fate
of each function in the `cast` module.
* transmute - This function was moved to `mem`, but it is now marked as
#[unstable]. This is due to planned changes to the `transmute`
function and how it can be invoked (see the #[unstable] comment).
For more information, see RFC 5 and #12898
* transmute_copy - This function was moved to `mem`, with clarification that is
is not an error to invoke it with T/U that are different
sizes, but rather that it is strongly discouraged. This
function is now #[stable]
* forget - This function was moved to `mem` and marked #[stable]
* bump_box_refcount - This function was removed due to the deprecation of
managed boxes as well as its questionable utility.
* transmute_mut - This function was previously deprecated, and removed as part
of this commit.
* transmute_mut_unsafe - This function doesn't serve much of a purpose when it
can be achieved with an `as` in safe code, so it was
removed.
* transmute_lifetime - This function was removed because it is likely a strong
indication that code is incorrect in the first place.
* transmute_mut_lifetime - This function was removed for the same reasons as
`transmute_lifetime`
* copy_lifetime - This function was moved to `mem`, but it is marked
`#[unstable]` now due to the likelihood of being removed in
the future if it is found to not be very useful.
* copy_mut_lifetime - This function was also moved to `mem`, but had the same
treatment as `copy_lifetime`.
* copy_lifetime_vec - This function was removed because it is not used today,
and its existence is not necessary with DST
(copy_lifetime will suffice).
In summary, the cast module was stripped down to these functions, and then the
functions were moved to the `mem` module.
transmute - #[unstable]
transmute_copy - #[stable]
forget - #[stable]
copy_lifetime - #[unstable]
copy_mut_lifetime - #[unstable]
[breaking-change]
2014-05-09 10:34:51 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/// Transforms lifetime of the second pointer to match the first.
|
|
|
|
#[inline]
|
|
|
|
#[unstable = "this function may be removed in the future due to its \
|
|
|
|
questionable utility"]
|
2014-08-27 21:46:52 -04:00
|
|
|
pub unsafe fn copy_lifetime<'a, S, T:'a>(_ptr: &'a S, ptr: &T) -> &'a T {
|
core: Remove the cast module
This commit revisits the `cast` module in libcore and libstd, and scrutinizes
all functions inside of it. The result was to remove the `cast` module entirely,
folding all functionality into the `mem` module. Specifically, this is the fate
of each function in the `cast` module.
* transmute - This function was moved to `mem`, but it is now marked as
#[unstable]. This is due to planned changes to the `transmute`
function and how it can be invoked (see the #[unstable] comment).
For more information, see RFC 5 and #12898
* transmute_copy - This function was moved to `mem`, with clarification that is
is not an error to invoke it with T/U that are different
sizes, but rather that it is strongly discouraged. This
function is now #[stable]
* forget - This function was moved to `mem` and marked #[stable]
* bump_box_refcount - This function was removed due to the deprecation of
managed boxes as well as its questionable utility.
* transmute_mut - This function was previously deprecated, and removed as part
of this commit.
* transmute_mut_unsafe - This function doesn't serve much of a purpose when it
can be achieved with an `as` in safe code, so it was
removed.
* transmute_lifetime - This function was removed because it is likely a strong
indication that code is incorrect in the first place.
* transmute_mut_lifetime - This function was removed for the same reasons as
`transmute_lifetime`
* copy_lifetime - This function was moved to `mem`, but it is marked
`#[unstable]` now due to the likelihood of being removed in
the future if it is found to not be very useful.
* copy_mut_lifetime - This function was also moved to `mem`, but had the same
treatment as `copy_lifetime`.
* copy_lifetime_vec - This function was removed because it is not used today,
and its existence is not necessary with DST
(copy_lifetime will suffice).
In summary, the cast module was stripped down to these functions, and then the
functions were moved to the `mem` module.
transmute - #[unstable]
transmute_copy - #[stable]
forget - #[stable]
copy_lifetime - #[unstable]
copy_mut_lifetime - #[unstable]
[breaking-change]
2014-05-09 10:34:51 -07:00
|
|
|
transmute(ptr)
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Transforms lifetime of the second mutable pointer to match the first.
|
|
|
|
#[inline]
|
|
|
|
#[unstable = "this function may be removed in the future due to its \
|
|
|
|
questionable utility"]
|
2014-08-27 21:46:52 -04:00
|
|
|
pub unsafe fn copy_mut_lifetime<'a, S, T:'a>(_ptr: &'a mut S,
|
core: Remove the cast module
This commit revisits the `cast` module in libcore and libstd, and scrutinizes
all functions inside of it. The result was to remove the `cast` module entirely,
folding all functionality into the `mem` module. Specifically, this is the fate
of each function in the `cast` module.
* transmute - This function was moved to `mem`, but it is now marked as
#[unstable]. This is due to planned changes to the `transmute`
function and how it can be invoked (see the #[unstable] comment).
For more information, see RFC 5 and #12898
* transmute_copy - This function was moved to `mem`, with clarification that is
is not an error to invoke it with T/U that are different
sizes, but rather that it is strongly discouraged. This
function is now #[stable]
* forget - This function was moved to `mem` and marked #[stable]
* bump_box_refcount - This function was removed due to the deprecation of
managed boxes as well as its questionable utility.
* transmute_mut - This function was previously deprecated, and removed as part
of this commit.
* transmute_mut_unsafe - This function doesn't serve much of a purpose when it
can be achieved with an `as` in safe code, so it was
removed.
* transmute_lifetime - This function was removed because it is likely a strong
indication that code is incorrect in the first place.
* transmute_mut_lifetime - This function was removed for the same reasons as
`transmute_lifetime`
* copy_lifetime - This function was moved to `mem`, but it is marked
`#[unstable]` now due to the likelihood of being removed in
the future if it is found to not be very useful.
* copy_mut_lifetime - This function was also moved to `mem`, but had the same
treatment as `copy_lifetime`.
* copy_lifetime_vec - This function was removed because it is not used today,
and its existence is not necessary with DST
(copy_lifetime will suffice).
In summary, the cast module was stripped down to these functions, and then the
functions were moved to the `mem` module.
transmute - #[unstable]
transmute_copy - #[stable]
forget - #[stable]
copy_lifetime - #[unstable]
copy_mut_lifetime - #[unstable]
[breaking-change]
2014-05-09 10:34:51 -07:00
|
|
|
ptr: &mut T) -> &'a mut T {
|
|
|
|
transmute(ptr)
|
|
|
|
}
|