daemonic_error 1.0.0

Errors that compose, predict, and leave receipts - Compose: algebraic combination (in active development) - Predict: Glass/Severity - Receipts: audit trail, position, checksum - Reflection: Runtime Reflection through TopologySegment (in active development) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

use crate::daemonic::glass::Glass;
use crate::DaemonicError;

/// Information lost. Structure holds but data is incomplete.
/// Unlike Cracked, Fractured CAN cascade.
pub trait GlassFractured<GLASS>: Glass<GLASS> + for<'error> DaemonicError<'error> {
	/// What was lost? Human-readable description.
	fn loss_description(&self) -> &str;
	
	/// How much of the original survived? 0.0 to 1.0
	/// This needs to be more intelligent somehow.
	fn salvage_ratio(&self) -> f64 {
		match self.payload() {
			Some(_) => 0.5, // something survived, rough default
			None => 0.0,
		}
	}
	
	/// Attempt repair. Same pattern as Cracked but for
	/// information reconstruction, not containment.
	fn repair(&self) -> Option<&dyn Fn() -> GLASS> { None }
	/// By default, fractured states are flagged as "should not continue"
	fn should_continue(&self) -> bool { false }
}
/// Annotation on a Fractured observation.
/// "Information was lost, here's what and here's how to maybe get it back."
pub trait FracturedAnnotation<GLASS>: GlassFractured<GLASS> {
	fn annotation(&self) -> &str;
	
	/// What specific information was lost?
	fn loss_detail(&self) -> &str;
	
	/// Suggested recovery strategy, if any.
	fn recovery_strategy(&self) -> Option<&str> { None }
}