Skip to main content

Crate rusty_rtos_heap_core

Crate rusty_rtos_heap_core 

Source
Expand description

rusty_rtos_heap-core — the pure heart of rusty_rtos_heap.

Rules this crate lives by (from the Kairos mission plan):

  1. no_std by default; alloc is a feature, never an assumption.
  2. No CPU, no registers, no allocator, no operating system. Ports and backends are separate WRAP crates.
  3. Every type that crosses to another Kairos package comes from rusty_rtos_core, so packages compose without conversions.
  4. Handles are indices, never pointers; nothing on a hot path allocates.
  5. 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.c over an N-byte arena: allocate, never free.
heap3
heap_3.c: the platform’s allocator behind the family’s heap surface.
heap4
heap_4 remade: 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.