Expand description
rusty_rtos_heap-core — the pure heart of rusty_rtos_heap.
Rules this crate lives by (from the Kairos mission plan):
no_stdby default;allocis a feature, never an assumption.- No CPU, no registers, no allocator, no operating system. Ports and backends are separate WRAP crates.
- Every type that crosses to another Kairos package comes from
rusty_rtos_core, so packages compose without conversions. - Handles are indices, never pointers; nothing on a hot path allocates.
forbid(unsafe). The C kernel’s trace is the oracle; the scalar path is the oracle; any faster path is gated identical against it.
Re-exports§
pub use heap1::Heap1;pub use heap3::Heap3;pub use heap4::Heap4;pub use heap4::Region;pub use heap5::Heap5;pub use pool::Pool;pub use pool::Slot;pub use rusty_rtos_core as rtos_core;
Modules§
- heap1
heap_1.cover anN-byte arena: allocate, never free.- heap3
heap_3.c: the platform’s allocator behind the family’s heap surface.- heap4
heap_4remade: first fit with coalescing, byte for byte.- heap5
heap_5.c:heap_4’s free list, laid out over several regions.- pool
- A fixed-size block pool: the allocation an RTOS actually makes.
- prelude
- The names a firmware wants in scope.
Constants§
- VERSION
- Crate version, for manifests and logs.