Slots

This crate provides a heapless slab allocator with strict access control.

Slots implements a static friendly, fixed size, unordered data structure inspired by SlotMap. All operations are constant time.

Documentation

Features

• Slots provide the runtime_checks feature that can be used to disable key owner verification. By default the feature is on and it is recommended to leave it enabled for development builds and disabled for release builds.

  Note: This feature requires atomic instructions, which are not generally available (for example, on ARM Cortex-M0 microcontrollers)

lib.rs:

This crate provides a heapless, fixed size, unordered data structure, inspired by SlotMap.

The following basic operations (all of them O(1)) are defined for Slots:

• Store: store data and retrieve a handle for later access
• Read, modify: use the given handle to access the data without removal
• Take: use the given handle to remove data

There are two variations of this data structure:

• Slots, where elements can only be modified using a Key that can't be copied
• UnrestrictedSlots, where elements are free to be modified by anyone