Skip to main content

Module store

Module store 

Source
Expand description

The generic storage substrate trait and write-outcome types.

Structs§

Conflict
A detected concurrent-edit conflict: the caller’s write expected expected to be the current revision, but the store holds current. Surfaced, never silently resolved.

Enums§

DeleteResult
The outcome of a conditional delete. Like a Conflict from put, a Conflict here is a normal, recoverable result — not an error.
PutResult
The outcome of a conditional write. Conflict is a normal, recoverable result — not an error.

Traits§

BlobStore
A content-addressed blob store for out-of-line record bodies (Body::Blob). Content is keyed by its ContentHash, so byte-identical bodies — e.g. code-graph slices shared across worktrees (ADR 0012) — are stored once. Writes are write-if-absent: storing content that already exists is an idempotent no-op, never a conflict (same hash ⇒ same bytes).
Store
A pluggable storage substrate over generic records.