Struct CaptureMemory 

pub struct CaptureMemory { /* private fields */ }

What: The memory of landed captures, owned by the serve loop that lands the commits and answers the clients. Why: Only that one thread records a landed commit and reads the memory to answer a commit sent back, so the memory is a plain value it holds and passes down (&mut to record, & to read), not a process-wide table behind a lock: nothing waits for it and nothing else can reach it.

In TS you’d write (pseudocode):

const memory = new CaptureMemory(); memory.recordLanded(commonDir, worktree, commit, captured);

Implementations

impl CaptureMemory

Methods over the memory.

pub fn record_landed( &mut self, common_dir: &Path, worktree: &Path, commit: &str, captured: u64, )

What: Remembers a landed commit and the stamp of the request that made it, when the stamp is known. Why: A request with no stamp (zero) cannot be ordered, so it is not remembered and its commit stays unknown.

In TS you’d write (pseudocode):

memory.recordLanded(commonDir, worktree, commit, captured)

pub fn remembered( &self, common_dir: &Path, worktree: &Path, ) -> Vec<LandedCapture>

What: The commits landed for a worktree that the service remembers, oldest first. Why: The client matches them by name against the commits that changed a path since its base, so older ones do no harm.

In TS you’d write (pseudocode):

memory.remembered(commonDir, worktree)

Trait Implementations

impl Debug for CaptureMemory

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

Formats the value using the given formatter.

impl Default for CaptureMemory

fn default() -> Self

Returns the “default value” for a type.