pub struct Rc<T: ?Sized, A: Allocator = Global> { /* private fields */ }
Expand description
A single-threaded reference-counting pointer. ‘Rc’ stands for ‘Reference Counted’.
See the module-level documentation for more details.
The inherent methods of Rc
are all associated functions, which means
that you have to call them as e.g., Rc::get_mut(&mut value)
instead of
value.get_mut()
. This avoids conflicts with methods of the inner type T
.
Implementations§
Source§impl<T> Rc<T>
impl<T> Rc<T>
1.60.0 · Sourcepub fn new_cyclic<F>(data_fn: F) -> Rc<T>
pub fn new_cyclic<F>(data_fn: F) -> Rc<T>
Constructs a new Rc<T>
while giving you a Weak<T>
to the allocation,
to allow you to construct a T
which holds a weak pointer to itself.
Generally, a structure circularly referencing itself, either directly or
indirectly, should not hold a strong reference to itself to prevent a memory leak.
Using this function, you get access to the weak pointer during the
initialization of T
, before the Rc<T>
is created, such that you can
clone and store it inside the T
.
new_cyclic
first allocates the managed allocation for the Rc<T>
,
then calls your closure, giving it a Weak<T>
to this allocation,
and only afterwards completes the construction of the Rc<T>
by placing
the T
returned from your closure into the allocation.
Since the new Rc<T>
is not fully-constructed until Rc<T>::new_cyclic
returns, calling upgrade
on the weak reference inside your closure will
fail and result in a None
value.
§Panics
If data_fn
panics, the panic is propagated to the caller, and the
temporary Weak<T>
is dropped normally.
§Examples
use std::rc::{Rc, Weak};
struct Gadget {
me: Weak<Gadget>,
}
impl Gadget {
/// Constructs a reference counted Gadget.
fn new() -> Rc<Self> {
// `me` is a `Weak<Gadget>` pointing at the new allocation of the
// `Rc` we're constructing.
Rc::new_cyclic(|me| {
// Create the actual struct here.
Gadget { me: me.clone() }
})
}
/// Returns a reference counted pointer to Self.
fn me(&self) -> Rc<Self> {
self.me.upgrade().unwrap()
}
}
1.82.0 · Sourcepub fn new_uninit() -> Rc<MaybeUninit<T>>
pub fn new_uninit() -> Rc<MaybeUninit<T>>
Constructs a new Rc
with uninitialized contents.
§Examples
Sourcepub fn new_zeroed() -> Rc<MaybeUninit<T>>
🔬This is a nightly-only experimental API. (new_zeroed_alloc
#129396)
pub fn new_zeroed() -> Rc<MaybeUninit<T>>
new_zeroed_alloc
#129396)Constructs a new Rc
with uninitialized contents, with the memory
being filled with 0
bytes.
See MaybeUninit::zeroed
for examples of correct and
incorrect usage of this method.
§Examples
Sourcepub fn try_new(value: T) -> Result<Rc<T>, AllocError>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn try_new(value: T) -> Result<Rc<T>, AllocError>
allocator_api
#32838)Constructs a new Rc<T>
, returning an error if the allocation fails
§Examples
Sourcepub fn try_new_uninit() -> Result<Rc<MaybeUninit<T>>, AllocError>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn try_new_uninit() -> Result<Rc<MaybeUninit<T>>, AllocError>
allocator_api
#32838)Constructs a new Rc
with uninitialized contents, returning an error if the allocation fails
§Examples
Sourcepub fn try_new_zeroed() -> Result<Rc<MaybeUninit<T>>, AllocError>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn try_new_zeroed() -> Result<Rc<MaybeUninit<T>>, AllocError>
allocator_api
#32838)Constructs a new Rc
with uninitialized contents, with the memory
being filled with 0
bytes, returning an error if the allocation fails
See MaybeUninit::zeroed
for examples of correct and
incorrect usage of this method.
§Examples
Source§impl<T, A: Allocator> Rc<T, A>
impl<T, A: Allocator> Rc<T, A>
Sourcepub fn new_in(value: T, alloc: A) -> Rc<T, A>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn new_in(value: T, alloc: A) -> Rc<T, A>
allocator_api
#32838)Constructs a new Rc
in the provided allocator.
§Examples
Sourcepub fn new_uninit_in(alloc: A) -> Rc<MaybeUninit<T>, A>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn new_uninit_in(alloc: A) -> Rc<MaybeUninit<T>, A>
allocator_api
#32838)Constructs a new Rc
with uninitialized contents in the provided allocator.
§Examples
Sourcepub fn new_zeroed_in(alloc: A) -> Rc<MaybeUninit<T>, A>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn new_zeroed_in(alloc: A) -> Rc<MaybeUninit<T>, A>
allocator_api
#32838)Constructs a new Rc
with uninitialized contents, with the memory
being filled with 0
bytes, in the provided allocator.
See MaybeUninit::zeroed
for examples of correct and
incorrect usage of this method.
§Examples
Sourcepub fn new_cyclic_in<F>(data_fn: F, alloc: A) -> Rc<T, A>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn new_cyclic_in<F>(data_fn: F, alloc: A) -> Rc<T, A>
allocator_api
#32838)Constructs a new Rc<T, A>
in the given allocator while giving you a Weak<T, A>
to the allocation,
to allow you to construct a T
which holds a weak pointer to itself.
Generally, a structure circularly referencing itself, either directly or
indirectly, should not hold a strong reference to itself to prevent a memory leak.
Using this function, you get access to the weak pointer during the
initialization of T
, before the Rc<T, A>
is created, such that you can
clone and store it inside the T
.
new_cyclic_in
first allocates the managed allocation for the Rc<T, A>
,
then calls your closure, giving it a Weak<T, A>
to this allocation,
and only afterwards completes the construction of the Rc<T, A>
by placing
the T
returned from your closure into the allocation.
Since the new Rc<T, A>
is not fully-constructed until Rc<T, A>::new_cyclic_in
returns, calling upgrade
on the weak reference inside your closure will
fail and result in a None
value.
§Panics
If data_fn
panics, the panic is propagated to the caller, and the
temporary Weak<T, A>
is dropped normally.
§Examples
See new_cyclic
.
Sourcepub fn try_new_in(value: T, alloc: A) -> Result<Self, AllocError>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn try_new_in(value: T, alloc: A) -> Result<Self, AllocError>
allocator_api
#32838)Constructs a new Rc<T>
in the provided allocator, returning an error if the allocation
fails
§Examples
Sourcepub fn try_new_uninit_in(alloc: A) -> Result<Rc<MaybeUninit<T>, A>, AllocError>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn try_new_uninit_in(alloc: A) -> Result<Rc<MaybeUninit<T>, A>, AllocError>
allocator_api
#32838)Constructs a new Rc
with uninitialized contents, in the provided allocator, returning an
error if the allocation fails
§Examples
#![feature(allocator_api)]
#![feature(get_mut_unchecked)]
use std::rc::Rc;
use std::alloc::System;
let mut five = Rc::<u32, _>::try_new_uninit_in(System)?;
let five = unsafe {
// Deferred initialization:
Rc::get_mut_unchecked(&mut five).as_mut_ptr().write(5);
five.assume_init()
};
assert_eq!(*five, 5);
Sourcepub fn try_new_zeroed_in(alloc: A) -> Result<Rc<MaybeUninit<T>, A>, AllocError>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn try_new_zeroed_in(alloc: A) -> Result<Rc<MaybeUninit<T>, A>, AllocError>
allocator_api
#32838)Constructs a new Rc
with uninitialized contents, with the memory
being filled with 0
bytes, in the provided allocator, returning an error if the allocation
fails
See MaybeUninit::zeroed
for examples of correct and
incorrect usage of this method.
§Examples
Sourcepub fn pin_in(value: T, alloc: A) -> Pin<Self>where
A: 'static,
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn pin_in(value: T, alloc: A) -> Pin<Self>where
A: 'static,
allocator_api
#32838)Constructs a new Pin<Rc<T>>
in the provided allocator. If T
does not implement Unpin
, then
value
will be pinned in memory and unable to be moved.
1.4.0 · Sourcepub fn try_unwrap(this: Self) -> Result<T, Self>
pub fn try_unwrap(this: Self) -> Result<T, Self>
1.70.0 · Sourcepub fn into_inner(this: Self) -> Option<T>
pub fn into_inner(this: Self) -> Option<T>
Returns the inner value, if the Rc
has exactly one strong reference.
Otherwise, None
is returned and the Rc
is dropped.
This will succeed even if there are outstanding weak references.
If Rc::into_inner
is called on every clone of this Rc
,
it is guaranteed that exactly one of the calls returns the inner value.
This means in particular that the inner value is not dropped.
Rc::try_unwrap
is conceptually similar to Rc::into_inner
.
And while they are meant for different use-cases, Rc::into_inner(this)
is in fact equivalent to Rc::try_unwrap(this).ok()
.
(Note that the same kind of equivalence does not hold true for
Arc
, due to race conditions that do not apply to Rc
!)
§Examples
Source§impl<T> Rc<[T]>
impl<T> Rc<[T]>
1.82.0 · Sourcepub fn new_uninit_slice(len: usize) -> Rc<[MaybeUninit<T>]>
pub fn new_uninit_slice(len: usize) -> Rc<[MaybeUninit<T>]>
Constructs a new reference-counted slice with uninitialized contents.
§Examples
#![feature(get_mut_unchecked)]
use std::rc::Rc;
let mut values = Rc::<[u32]>::new_uninit_slice(3);
// Deferred initialization:
let data = Rc::get_mut(&mut values).unwrap();
data[0].write(1);
data[1].write(2);
data[2].write(3);
let values = unsafe { values.assume_init() };
assert_eq!(*values, [1, 2, 3])
Sourcepub fn new_zeroed_slice(len: usize) -> Rc<[MaybeUninit<T>]>
🔬This is a nightly-only experimental API. (new_zeroed_alloc
#129396)
pub fn new_zeroed_slice(len: usize) -> Rc<[MaybeUninit<T>]>
new_zeroed_alloc
#129396)Constructs a new reference-counted slice with uninitialized contents, with the memory being
filled with 0
bytes.
See MaybeUninit::zeroed
for examples of correct and
incorrect usage of this method.
§Examples
Source§impl<T, A: Allocator> Rc<[T], A>
impl<T, A: Allocator> Rc<[T], A>
Sourcepub fn new_uninit_slice_in(len: usize, alloc: A) -> Rc<[MaybeUninit<T>], A>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn new_uninit_slice_in(len: usize, alloc: A) -> Rc<[MaybeUninit<T>], A>
allocator_api
#32838)Constructs a new reference-counted slice with uninitialized contents.
§Examples
#![feature(get_mut_unchecked)]
#![feature(allocator_api)]
use std::rc::Rc;
use std::alloc::System;
let mut values = Rc::<[u32], _>::new_uninit_slice_in(3, System);
let values = unsafe {
// Deferred initialization:
Rc::get_mut_unchecked(&mut values)[0].as_mut_ptr().write(1);
Rc::get_mut_unchecked(&mut values)[1].as_mut_ptr().write(2);
Rc::get_mut_unchecked(&mut values)[2].as_mut_ptr().write(3);
values.assume_init()
};
assert_eq!(*values, [1, 2, 3])
Sourcepub fn new_zeroed_slice_in(len: usize, alloc: A) -> Rc<[MaybeUninit<T>], A>
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn new_zeroed_slice_in(len: usize, alloc: A) -> Rc<[MaybeUninit<T>], A>
allocator_api
#32838)Constructs a new reference-counted slice with uninitialized contents, with the memory being
filled with 0
bytes.
See MaybeUninit::zeroed
for examples of correct and
incorrect usage of this method.
§Examples
Source§impl<T, A: Allocator> Rc<MaybeUninit<T>, A>
impl<T, A: Allocator> Rc<MaybeUninit<T>, A>
1.82.0 · Sourcepub unsafe fn assume_init(self) -> Rc<T, A>
pub unsafe fn assume_init(self) -> Rc<T, A>
Converts to Rc<T>
.
§Safety
As with MaybeUninit::assume_init
,
it is up to the caller to guarantee that the inner value
really is in an initialized state.
Calling this when the content is not yet fully initialized
causes immediate undefined behavior.
§Examples
Source§impl<T, A: Allocator> Rc<[MaybeUninit<T>], A>
impl<T, A: Allocator> Rc<[MaybeUninit<T>], A>
1.82.0 · Sourcepub unsafe fn assume_init(self) -> Rc<[T], A>
pub unsafe fn assume_init(self) -> Rc<[T], A>
Converts to Rc<[T]>
.
§Safety
As with MaybeUninit::assume_init
,
it is up to the caller to guarantee that the inner value
really is in an initialized state.
Calling this when the content is not yet fully initialized
causes immediate undefined behavior.
§Examples
#![feature(get_mut_unchecked)]
use std::rc::Rc;
let mut values = Rc::<[u32]>::new_uninit_slice(3);
// Deferred initialization:
let data = Rc::get_mut(&mut values).unwrap();
data[0].write(1);
data[1].write(2);
data[2].write(3);
let values = unsafe { values.assume_init() };
assert_eq!(*values, [1, 2, 3])
Source§impl<T: ?Sized> Rc<T>
impl<T: ?Sized> Rc<T>
1.17.0 · Sourcepub unsafe fn from_raw(ptr: *const T) -> Self
pub unsafe fn from_raw(ptr: *const T) -> Self
Constructs an Rc<T>
from a raw pointer.
The raw pointer must have been previously returned by a call to
Rc<U>::into_raw
with the following requirements:
- If
U
is sized, it must have the same size and alignment asT
. This is trivially true ifU
isT
. - If
U
is unsized, its data pointer must have the same size and alignment asT
. This is trivially true ifRc<U>
was constructed throughRc<T>
and then converted toRc<U>
through an unsized coercion.
Note that if U
or U
’s data pointer is not T
but has the same size
and alignment, this is basically like transmuting references of
different types. See mem::transmute
for more information
on what restrictions apply in this case.
The raw pointer must point to a block of memory allocated by the global allocator
The user of from_raw
has to make sure a specific value of T
is only
dropped once.
This function is unsafe because improper use may lead to memory unsafety,
even if the returned Rc<T>
is never accessed.
§Examples
use std::rc::Rc;
let x = Rc::new("hello".to_owned());
let x_ptr = Rc::into_raw(x);
unsafe {
// Convert back to an `Rc` to prevent leak.
let x = Rc::from_raw(x_ptr);
assert_eq!(&*x, "hello");
// Further calls to `Rc::from_raw(x_ptr)` would be memory-unsafe.
}
// The memory was freed when `x` went out of scope above, so `x_ptr` is now dangling!
Convert a slice back into its original array:
1.53.0 · Sourcepub unsafe fn increment_strong_count(ptr: *const T)
pub unsafe fn increment_strong_count(ptr: *const T)
Increments the strong reference count on the Rc<T>
associated with the
provided pointer by one.
§Safety
The pointer must have been obtained through Rc::into_raw
, the
associated Rc
instance must be valid (i.e. the strong count must be at
least 1) for the duration of this method, and ptr
must point to a block of memory
allocated by the global allocator.
§Examples
1.53.0 · Sourcepub unsafe fn decrement_strong_count(ptr: *const T)
pub unsafe fn decrement_strong_count(ptr: *const T)
Decrements the strong reference count on the Rc<T>
associated with the
provided pointer by one.
§Safety
The pointer must have been obtained through Rc::into_raw
, the
associated Rc
instance must be valid (i.e. the strong count must be at
least 1) when invoking this method, and ptr
must point to a block of memory
allocated by the global allocator. This method can be used to release the final Rc
and
backing storage, but should not be called after the final Rc
has been released.
§Examples
Source§impl<T: ?Sized, A: Allocator> Rc<T, A>
impl<T: ?Sized, A: Allocator> Rc<T, A>
Sourcepub fn allocator(this: &Self) -> &A
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn allocator(this: &Self) -> &A
allocator_api
#32838)Returns a reference to the underlying allocator.
Note: this is an associated function, which means that you have
to call it as Rc::allocator(&r)
instead of r.allocator()
. This
is so that there is no conflict with a method on the inner type.
1.17.0 · Sourcepub fn into_raw(this: Self) -> *const T
pub fn into_raw(this: Self) -> *const T
Consumes the Rc
, returning the wrapped pointer.
To avoid a memory leak the pointer must be converted back to an Rc
using
Rc::from_raw
.
§Examples
Sourcepub fn into_raw_with_allocator(this: Self) -> (*const T, A)
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub fn into_raw_with_allocator(this: Self) -> (*const T, A)
allocator_api
#32838)Consumes the Rc
, returning the wrapped pointer and allocator.
To avoid a memory leak the pointer must be converted back to an Rc
using
Rc::from_raw_in
.
§Examples
1.45.0 · Sourcepub fn as_ptr(this: &Self) -> *const T
pub fn as_ptr(this: &Self) -> *const T
Provides a raw pointer to the data.
The counts are not affected in any way and the Rc
is not consumed. The pointer is valid
for as long there are strong counts in the Rc
.
§Examples
Sourcepub unsafe fn from_raw_in(ptr: *const T, alloc: A) -> Self
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub unsafe fn from_raw_in(ptr: *const T, alloc: A) -> Self
allocator_api
#32838)Constructs an Rc<T, A>
from a raw pointer in the provided allocator.
The raw pointer must have been previously returned by a call to Rc<U, A>::into_raw
with the following requirements:
- If
U
is sized, it must have the same size and alignment asT
. This is trivially true ifU
isT
. - If
U
is unsized, its data pointer must have the same size and alignment asT
. This is trivially true ifRc<U>
was constructed throughRc<T>
and then converted toRc<U>
through an unsized coercion.
Note that if U
or U
’s data pointer is not T
but has the same size
and alignment, this is basically like transmuting references of
different types. See mem::transmute
for more information
on what restrictions apply in this case.
The raw pointer must point to a block of memory allocated by alloc
The user of from_raw
has to make sure a specific value of T
is only
dropped once.
This function is unsafe because improper use may lead to memory unsafety,
even if the returned Rc<T>
is never accessed.
§Examples
#![feature(allocator_api)]
use std::rc::Rc;
use std::alloc::System;
let x = Rc::new_in("hello".to_owned(), System);
let x_ptr = Rc::into_raw(x);
unsafe {
// Convert back to an `Rc` to prevent leak.
let x = Rc::from_raw_in(x_ptr, System);
assert_eq!(&*x, "hello");
// Further calls to `Rc::from_raw(x_ptr)` would be memory-unsafe.
}
// The memory was freed when `x` went out of scope above, so `x_ptr` is now dangling!
Convert a slice back into its original array:
1.15.0 · Sourcepub fn weak_count(this: &Self) -> usize
pub fn weak_count(this: &Self) -> usize
1.15.0 · Sourcepub fn strong_count(this: &Self) -> usize
pub fn strong_count(this: &Self) -> usize
Gets the number of strong (Rc
) pointers to this allocation.
§Examples
Sourcepub unsafe fn increment_strong_count_in(ptr: *const T, alloc: A)where
A: Clone,
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub unsafe fn increment_strong_count_in(ptr: *const T, alloc: A)where
A: Clone,
allocator_api
#32838)Increments the strong reference count on the Rc<T>
associated with the
provided pointer by one.
§Safety
The pointer must have been obtained through Rc::into_raw
, the
associated Rc
instance must be valid (i.e. the strong count must be at
least 1) for the duration of this method, and ptr
must point to a block of memory
allocated by alloc
§Examples
Sourcepub unsafe fn decrement_strong_count_in(ptr: *const T, alloc: A)
🔬This is a nightly-only experimental API. (allocator_api
#32838)
pub unsafe fn decrement_strong_count_in(ptr: *const T, alloc: A)
allocator_api
#32838)Decrements the strong reference count on the Rc<T>
associated with the
provided pointer by one.
§Safety
The pointer must have been obtained through Rc::into_raw
, the
associated Rc
instance must be valid (i.e. the strong count must be at
least 1) when invoking this method, and ptr
must point to a block of memory
allocated by alloc
. This method can be used to release the final Rc
and backing storage,
but should not be called after the final Rc
has been released.
§Examples
#![feature(allocator_api)]
use std::rc::Rc;
use std::alloc::System;
let five = Rc::new_in(5, System);
unsafe {
let ptr = Rc::into_raw(five);
Rc::increment_strong_count_in(ptr, System);
let five = Rc::from_raw_in(ptr, System);
assert_eq!(2, Rc::strong_count(&five));
Rc::decrement_strong_count_in(ptr, System);
assert_eq!(1, Rc::strong_count(&five));
}
1.4.0 · Sourcepub fn get_mut(this: &mut Self) -> Option<&mut T>
pub fn get_mut(this: &mut Self) -> Option<&mut T>
Sourcepub unsafe fn get_mut_unchecked(this: &mut Self) -> &mut T
🔬This is a nightly-only experimental API. (get_mut_unchecked
#63292)
pub unsafe fn get_mut_unchecked(this: &mut Self) -> &mut T
get_mut_unchecked
#63292)Returns a mutable reference into the given Rc
,
without any check.
See also get_mut
, which is safe and does appropriate checks.
§Safety
If any other Rc
or Weak
pointers to the same allocation exist, then
they must not be dereferenced or have active borrows for the duration
of the returned borrow, and their inner type must be exactly the same as the
inner type of this Rc (including lifetimes). This is trivially the case if no
such pointers exist, for example immediately after Rc::new
.
§Examples
#![feature(get_mut_unchecked)]
use std::rc::Rc;
let mut x = Rc::new(String::new());
unsafe {
Rc::get_mut_unchecked(&mut x).push_str("foo")
}
assert_eq!(*x, "foo");
Other Rc
pointers to the same allocation must be to the same type.
#![feature(get_mut_unchecked)]
use std::rc::Rc;
let x: Rc<str> = Rc::from("Hello, world!");
let mut y: Rc<[u8]> = x.clone().into();
unsafe {
// this is Undefined Behavior, because x's inner type is str, not [u8]
Rc::get_mut_unchecked(&mut y).fill(0xff); // 0xff is invalid in UTF-8
}
println!("{}", &*x); // Invalid UTF-8 in a str
Other Rc
pointers to the same allocation must be to the exact same type, including lifetimes.
#![feature(get_mut_unchecked)]
use std::rc::Rc;
let x: Rc<&str> = Rc::new("Hello, world!");
{
let s = String::from("Oh, no!");
let mut y: Rc<&str> = x.clone().into();
unsafe {
// this is Undefined Behavior, because x's inner type
// is &'long str, not &'short str
*Rc::get_mut_unchecked(&mut y) = &s;
}
}
println!("{}", &*x); // Use-after-free
Source§impl<T: ?Sized + CloneToUninit, A: Allocator + Clone> Rc<T, A>
impl<T: ?Sized + CloneToUninit, A: Allocator + Clone> Rc<T, A>
1.4.0 · Sourcepub fn make_mut(this: &mut Self) -> &mut T
pub fn make_mut(this: &mut Self) -> &mut T
Makes a mutable reference into the given Rc
.
If there are other Rc
pointers to the same allocation, then make_mut
will
clone
the inner value to a new allocation to ensure unique ownership. This is also
referred to as clone-on-write.
However, if there are no other Rc
pointers to this allocation, but some Weak
pointers, then the Weak
pointers will be disassociated and the inner value will not
be cloned.
See also get_mut
, which will fail rather than cloning the inner value
or disassociating Weak
pointers.
§Examples
use std::rc::Rc;
let mut data = Rc::new(5);
*Rc::make_mut(&mut data) += 1; // Won't clone anything
let mut other_data = Rc::clone(&data); // Won't clone inner data
*Rc::make_mut(&mut data) += 1; // Clones inner data
*Rc::make_mut(&mut data) += 1; // Won't clone anything
*Rc::make_mut(&mut other_data) *= 2; // Won't clone anything
// Now `data` and `other_data` point to different allocations.
assert_eq!(*data, 8);
assert_eq!(*other_data, 12);
Weak
pointers will be disassociated:
Source§impl<T: Clone, A: Allocator> Rc<T, A>
impl<T: Clone, A: Allocator> Rc<T, A>
1.76.0 · Sourcepub fn unwrap_or_clone(this: Self) -> T
pub fn unwrap_or_clone(this: Self) -> T
If we have the only reference to T
then unwrap it. Otherwise, clone T
and return the
clone.
Assuming rc_t
is of type Rc<T>
, this function is functionally equivalent to
(*rc_t).clone()
, but will avoid cloning the inner value where possible.
§Examples
let inner = String::from("test");
let ptr = inner.as_ptr();
let rc = Rc::new(inner);
let inner = Rc::unwrap_or_clone(rc);
// The inner value was not cloned
assert!(ptr::eq(ptr, inner.as_ptr()));
let rc = Rc::new(inner);
let rc2 = rc.clone();
let inner = Rc::unwrap_or_clone(rc);
// Because there were 2 references, we had to clone the inner value.
assert!(!ptr::eq(ptr, inner.as_ptr()));
// `rc2` is the last reference, so when we unwrap it we get back
// the original `String`.
let inner = Rc::unwrap_or_clone(rc2);
assert!(ptr::eq(ptr, inner.as_ptr()));
Source§impl<A: Allocator> Rc<dyn Any, A>
impl<A: Allocator> Rc<dyn Any, A>
1.29.0 · Sourcepub fn downcast<T: Any>(self) -> Result<Rc<T, A>, Self>
pub fn downcast<T: Any>(self) -> Result<Rc<T, A>, Self>
Attempts to downcast the Rc<dyn Any>
to a concrete type.
§Examples
Sourcepub unsafe fn downcast_unchecked<T: Any>(self) -> Rc<T, A>
🔬This is a nightly-only experimental API. (downcast_unchecked
#90850)
pub unsafe fn downcast_unchecked<T: Any>(self) -> Rc<T, A>
downcast_unchecked
#90850)Downcasts the Rc<dyn Any>
to a concrete type.
For a safe alternative see downcast
.
§Examples
#![feature(downcast_unchecked)]
use std::any::Any;
use std::rc::Rc;
let x: Rc<dyn Any> = Rc::new(1_usize);
unsafe {
assert_eq!(*x.downcast_unchecked::<usize>(), 1);
}
§Safety
The contained value must be of type T
. Calling this method
with the incorrect type is undefined behavior.
Trait Implementations§
1.0.0 · Source§impl<T: ?Sized, A: Allocator + Clone> Clone for Rc<T, A>
impl<T: ?Sized, A: Allocator + Clone> Clone for Rc<T, A>
1.0.0 · Source§impl<T: ?Sized, A: Allocator> Drop for Rc<T, A>
impl<T: ?Sized, A: Allocator> Drop for Rc<T, A>
Source§impl<W: LocalWake + 'static> From<Rc<W>> for LocalWaker
impl<W: LocalWake + 'static> From<Rc<W>> for LocalWaker
Source§fn from(waker: Rc<W>) -> LocalWaker
fn from(waker: Rc<W>) -> LocalWaker
Use a Wake
-able type as a LocalWaker
.
No heap allocations or atomic operations are used for this conversion.
1.37.0 · Source§impl<T> FromIterator<T> for Rc<[T]>
impl<T> FromIterator<T> for Rc<[T]>
Source§fn from_iter<I: IntoIterator<Item = T>>(iter: I) -> Self
fn from_iter<I: IntoIterator<Item = T>>(iter: I) -> Self
Takes each element in the Iterator
and collects it into an Rc<[T]>
.
§Performance characteristics
§The general case
In the general case, collecting into Rc<[T]>
is done by first
collecting into a Vec<T>
. That is, when writing the following:
this behaves as if we wrote:
let evens: Rc<[u8]> = (0..10).filter(|&x| x % 2 == 0)
.collect::<Vec<_>>() // The first set of allocations happens here.
.into(); // A second allocation for `Rc<[T]>` happens here.
This will allocate as many times as needed for constructing the Vec<T>
and then it will allocate once for turning the Vec<T>
into the Rc<[T]>
.
§Iterators of known length
When your Iterator
implements TrustedLen
and is of an exact size,
a single allocation will be made for the Rc<[T]>
. For example:
1.0.0 · Source§impl<T: ?Sized + Ord, A: Allocator> Ord for Rc<T, A>
impl<T: ?Sized + Ord, A: Allocator> Ord for Rc<T, A>
Source§fn cmp(&self, other: &Rc<T, A>) -> Ordering
fn cmp(&self, other: &Rc<T, A>) -> Ordering
1.21.0 · Source§fn max(self, other: Self) -> Selfwhere
Self: Sized,
fn max(self, other: Self) -> Selfwhere
Self: Sized,
1.0.0 · Source§impl<T: ?Sized + PartialEq, A: Allocator> PartialEq for Rc<T, A>
impl<T: ?Sized + PartialEq, A: Allocator> PartialEq for Rc<T, A>
Source§fn eq(&self, other: &Rc<T, A>) -> bool
fn eq(&self, other: &Rc<T, A>) -> bool
Equality for two Rc
s.
Two Rc
s are equal if their inner values are equal, even if they are
stored in different allocation.
If T
also implements Eq
(implying reflexivity of equality),
two Rc
s that point to the same allocation are
always equal.
§Examples
1.0.0 · Source§impl<T: ?Sized + PartialOrd, A: Allocator> PartialOrd for Rc<T, A>
impl<T: ?Sized + PartialOrd, A: Allocator> PartialOrd for Rc<T, A>
Source§fn partial_cmp(&self, other: &Rc<T, A>) -> Option<Ordering>
fn partial_cmp(&self, other: &Rc<T, A>) -> Option<Ordering>
Partial comparison for two Rc
s.
The two are compared by calling partial_cmp()
on their inner values.
§Examples
Source§fn lt(&self, other: &Rc<T, A>) -> bool
fn lt(&self, other: &Rc<T, A>) -> bool
Less-than comparison for two Rc
s.
The two are compared by calling <
on their inner values.
§Examples
Source§fn le(&self, other: &Rc<T, A>) -> bool
fn le(&self, other: &Rc<T, A>) -> bool
‘Less than or equal to’ comparison for two Rc
s.
The two are compared by calling <=
on their inner values.