pub struct Appender { /* private fields */ }Expand description
Append-only transcript authority.
Every method consumes an owned candidate before taking the commit lock. No user clone or callback runs while the write lock is held; after all checks, the ordered batch and version become visible in one critical section.
use reef_core::transcript::store;
let append = store::Store::new().appender();
append.replace(Vec::new());Implementations§
Source§impl Appender
impl Appender
Sourcepub fn append(&self, item: Item) -> Result<Version, Error>
pub fn append(&self, item: Item) -> Result<Version, Error>
Appends one owned item and advances the version by one.
§Errors
Error::VersionOverflow if the store already stands at
Version::MAX, and Error::Poisoned if a writer panicked while
holding the store lock. Either way the history is unchanged. There is no
conflict to report, because this append accepts whatever version it finds.
Sourcepub fn append_batch(&self, items: Vec<Item>) -> Result<Version, Error>
pub fn append_batch(&self, items: Vec<Item>) -> Result<Version, Error>
Atomically appends an owned ordered batch.
The version advances by items.len(). An empty batch is a successful
no-op which still reports lock poisoning.
§Errors
Error::VersionOverflow, reporting the current version and the
requested increment, if advancing by items.len() would pass
Version::MAX; and Error::Poisoned if a writer panicked while
holding the store lock. A failure appends none of the batch — this is the
atomicity the whole crate’s “never write half of an exchange” rule rests
on, so a rejected batch leaves no partial history behind.
Sourcepub fn append_batch_if_version(
&self,
items: Vec<Item>,
expected: Version,
) -> Result<Version, Error>
pub fn append_batch_if_version( &self, items: Vec<Item>, expected: Version, ) -> Result<Version, Error>
Atomically appends a batch only at expected.
Even an empty batch checks expected; conflicts and overflow leave both
history and version unchanged.
§Errors
Error::VersionConflict, reporting bothexpectedand the version actually observed under the commit lock, if another writer advanced the store after the caller readexpected. The concurrent winner is never overwritten; the loser is expected to re-read and decide again.Error::VersionOverflowif the batch would advance pastVersion::MAX. The conflict check runs first, so a stale caller hears about staleness rather than about a limit it may not be near.Error::Poisonedif a writer panicked while holding the store lock.