Struct PinnedPool

Source

pub struct PinnedPool<T: Send + 'static> { /* private fields */ }

Expand description

A thread-safe pool of reference-counted objects of type T.

All values in the pool remain pinned for their entire lifetime.

The pool automatically expands its capacity when needed.

§Lifetime management

When inserting an object into the pool, a handle to the object is returned. The object is removed from the pool when the last remaining handle to the object is dropped (Arc-like behavior).

Clones of the pool are functionally equivalent views over the same memory capacity.

§Thread safety

The pool is thread-safe.

§Example

use infinity_pool::PinnedPool;

let mut pool = PinnedPool::<String>::new();

// Insert an object into the pool
let handle = pool.insert("Hello, Pinned!".to_string());

// Access the object through the handle
assert_eq!(*handle, "Hello, Pinned!");

// The object is automatically removed when the handle is dropped

§Pool clones are functionally equivalent

use infinity_pool::PinnedPool;

let mut pool1 = PinnedPool::<i32>::new();
let pool2 = pool1.clone();

assert_eq!(pool1.len(), pool2.len());
let _handle = pool1.insert(42);
assert_eq!(pool1.len(), pool2.len());

The pool is thread-safe (Send and Sync) and requires T: Send.

Implementations§

Source §

impl<T> PinnedPool<T>
where T: Send + 'static,

Source

pub fn new() -> Self

Creates a new pool for objects of type T.

Source

pub fn len(&self) -> usize

The number of objects currently in the pool.

Source

pub fn capacity(&self) -> usize

The total capacity of the pool.

This is the maximum number of objects (including current contents) that the pool can contain without capacity extension. The pool will automatically extend its capacity if more than this many objects are inserted.

Source

pub fn is_empty(&self) -> bool

Whether the pool contains zero objects.

Source

pub fn reserve(&self, additional: usize)

Ensures that the pool has capacity for at least additional more objects.

§Panics

Panics if the new capacity would exceed the size of virtual memory (usize::MAX).

Source

pub fn shrink_to_fit(&self)

Drops unused pool capacity to reduce memory usage.

There is no guarantee that any unused capacity can be dropped. The exact outcome depends on the specific pool structure and which objects remain in the pool.

Source

pub fn insert(&self, value: T) -> PooledMut<T>

Inserts an object into the pool and returns a handle to it.

§Example

use infinity_pool::PinnedPool;

let mut pool = PinnedPool::<String>::new();

// Insert an object into the pool
let mut handle = pool.insert("Hello".to_string());

// Mutate the object via the unique handle
handle.push_str(", World!");
assert_eq!(&*handle, "Hello, World!");

// Transform the unique handle into a shared handle
let shared_handle = handle.into_shared();

// After transformation, you can only immutably dereference the object
assert_eq!(&*shared_handle, "Hello, World!");
// shared_handle.push_str("!"); // This would not compile

// The object is removed when the handle is dropped
drop(shared_handle); // Explicitly drop to remove from pool
assert_eq!(pool.len(), 0);

Source

pub unsafe fn insert_with<F>(&self, f: F) -> PooledMut<T>
where F: FnOnce(&mut MaybeUninit<T>),

Inserts an object into the pool via closure and returns a handle to it.

This method allows the caller to partially initialize the object, skipping any MaybeUninit fields that are intentionally not initialized at insertion time. This can make insertion of objects containing MaybeUninit fields faster, although requires unsafe code to implement.

This method is NOT faster than insert() for fully initialized objects. Prefer insert() for a better safety posture if you do not intend to skip initialization of any MaybeUninit fields.

§Example

use std::mem::MaybeUninit;

use infinity_pool::PinnedPool;

struct DataBuffer {
    id: u32,
    data: MaybeUninit<[u8; 1024]>, // Large buffer to skip initializing
}

let mut pool = PinnedPool::<DataBuffer>::new();

// Initialize only the id, leaving data uninitialized for performance
let handle = unsafe {
    pool.insert_with(|uninit: &mut MaybeUninit<DataBuffer>| {
        let ptr = uninit.as_mut_ptr();
        // SAFETY: Writing to the id field within allocated space
        unsafe {
            std::ptr::addr_of_mut!((*ptr).id).write(42);
            // data field is intentionally left uninitialized
        }
    })
};

// ID is accessible, data remains uninitialized
let id = unsafe { std::ptr::addr_of!((*handle).id).read() };
assert_eq!(id, 42);

§Safety

The closure must correctly initialize the object. All fields that are not MaybeUninit must be initialized when the closure returns.

Source

pub fn with_iter<F, R>(&self, f: F) -> R
where F: FnOnce(PinnedPoolIterator<'_, T>) -> R,

Calls a closure with an iterator over all objects in the pool.

The iterator only yields pointers to the objects, not references, because the pool does not have the authority to create references to its contents as user code may concurrently be holding a conflicting exclusive reference via PooledMut<T>.

Therefore, obtaining actual references to pool contents via iteration is only possible by using the pointer to create such references in unsafe code and relies on the caller guaranteeing that no conflicting exclusive references exist.

§Mutual exclusion

The pool is locked for the entire duration of the closure, ensuring that objects cannot be removed while iteration is in progress. This guarantees that all pointers yielded by the iterator remain valid for the duration of the closure.

§Examples

let mut pool = PinnedPool::<u32>::new();
let _handle1 = pool.insert(42u32);
let _handle2 = pool.insert(100u32);

// Safe iteration with guaranteed pointer validity
pool.with_iter(|iter| {
    for ptr in iter {
        // SAFETY: We know these are u32 pointers from this pool
        let value = unsafe { ptr.as_ref() };
        println!("Value: {}", value);
    }
});

// Collect values safely
let values: Vec<u32> =
    pool.with_iter(|iter| iter.map(|ptr| unsafe { *ptr.as_ref() }).collect());