pub struct ForgetPlan {
pub forgotten: Vec<String>,
pub invalidated: Vec<String>,
}Expand description
What a forgetting will do, computed over the namespace before anything is deleted: the explicitly forgotten records and the dependent summaries the erasure invalidates. Planning is a pure function of store state, so the route can journal exactly what it is about to do — the tombstone names this plan, and the deletion then executes it.
Fields§
§forgotten: Vec<String>The explicitly forgotten records (the targets that exist in the namespace), sorted for determinism.
invalidated: Vec<String>The dependent summaries invalidated by the erasure, sorted: every
summary record that names a removed record in
MemoryEvidence::source_memory_ids, transitively (a summary of
summaries goes too). They are deleted with the targets — a summary
built on erased evidence is derived state, and leaving it serving
content distilled from the forgotten record is not forgetting
(Cao & Yang’s point, per the design).
Trait Implementations§
Source§impl Clone for ForgetPlan
impl Clone for ForgetPlan
Source§fn clone(&self) -> ForgetPlan
fn clone(&self) -> ForgetPlan
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more