pub enum RefItemStatus {
Evaluated,
Failed {
message: String,
},
}Expand description
Outcome of attempting to classify one ref by name (DC-95 Stage 2 Level 2), after its pointer
and/or log file (whichever exist) were themselves read. No NotEvaluated distinct from
Failed: unlike Level 1’s stages or Phase B’s blocks, a ref has no peer ref it depends on –
its own pointer/log files are its own data, the same footing as an object’s own file in
verify_objects Phase A – so a failure attributable to this ref, whether from its own file
read or from classify_ref_state itself, is Failed, not a dependency-graph claim about
another item.
Variants§
Evaluated
This ref’s own classification (or its file reads, if either failed) resolved cleanly.
Failed
This ref’s pointer read, log read, or classify_ref_state call itself failed. Carries
whichever failure applies – a ref whose own pointer or log entry did not read is reported
through that entry’s real failure message, not reinterpreted as “pointer/log absent” (see
verify_refs’s own cross-referencing by ref_name_key_bytes, RFC 102 Stage 4).
Trait Implementations§
Source§impl Clone for RefItemStatus
impl Clone for RefItemStatus
Source§fn clone(&self) -> RefItemStatus
fn clone(&self) -> RefItemStatus
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more