Struct MemoryBackend 

pub struct MemoryBackend { /* private fields */ }

In-memory bytes backend backed by parking_lot::Mutex<HashMap<String, Vec<u8>>>. All operations are synchronous and in-process. Useful for tests, hot tiers, and as the default backend for the memory_* convenience factories.

Default uses "memory" as the diagnostic name; use Self::with_name to set a different one (the per-tier-name pattern from the TS impl — helps disambiguate multiple in-process tiers in diagnostics).

Implementations

impl MemoryBackend

pub fn new() -> Self

pub fn with_name(name: impl Into<String>) -> Self

pub fn len(&self) -> usize

Diagnostic helper: number of keys currently stored.

pub fn is_empty(&self) -> bool

Diagnostic helper: whether the backend holds any keys.

Trait Implementations

impl Debug for MemoryBackend

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for MemoryBackend

fn default() -> Self

Returns the “default value” for a type.

impl StorageBackend for MemoryBackend

fn name(&self) -> &str

Diagnostic name (e.g. "memory", "file:./checkpoints"). Surfaces in error messages and tier Display impls.

fn read(&self, key: &str) -> Result<Option<Vec<u8>>, StorageError>

Read raw bytes; returns Ok(None) on miss.

fn write(&self, key: &str, bytes: &[u8]) -> Result<(), StorageError>

Write raw bytes.

fn delete(&self, key: &str) -> Result<(), StorageError>

Optional delete-by-key. Default is no-op so append-only or read-only backends can stay quiet.

fn list(&self, prefix: &str) -> Result<Vec<String>, StorageError>

Enumerate keys matching prefix (lex-ASC). Empty prefix enumerates all keys. Default returns BackendNoListSupport — backends that don’t support enumeration surface the diagnostic here at first call, NOT at attach (mirrors TS lazy-throw semantics for list_by_prefix).

fn flush(&self) -> Result<(), StorageError>

Optional drain hook — adapter authors implement when buffering writes. Default no-op; tier flush() does NOT cascade into this by default (the tier owns its own buffer; backend buffering is a separate concern the backend author opts into).