pub enum TemporalAxis {
Present,
Past,
Future,
}Expand description
Represents the temporal axis in a UCXL address.
What: An enumeration of the three supported temporal positions – present, past, and future – each represented by a symbolic string in the address format.
How: The enum derives Debug, PartialEq, Eq, Clone, and Copy
for ergonomic usage. Conversions to and from strings are provided via the
FromStr and fmt::Display implementations.
Why: Temporal axes enable UCXL to refer to data at different points in time (e.g. versioned resources). The simple three‑state model matches the CHURUS architectural decision to keep addressing lightweight while still supporting historical and speculative queries.
Variants§
Present
Present (“#”) – the current version of a resource.
Past
Past (“~~”) – a historical snapshot of a resource.
Future
Future (“^^”) – a speculative or planned version of a resource.
Trait Implementations§
Source§impl Clone for TemporalAxis
impl Clone for TemporalAxis
Source§fn clone(&self) -> TemporalAxis
fn clone(&self) -> TemporalAxis
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for TemporalAxis
impl Debug for TemporalAxis
Source§impl Display for TemporalAxis
impl Display for TemporalAxis
Source§fn fmt(&self, f: &mut Formatter<'_>) -> Result
fn fmt(&self, f: &mut Formatter<'_>) -> Result
Formats the temporal axis back to its string token.
What: Returns “#”, “~~” or “^^” depending on the variant.
How: Matches on self and writes the corresponding string to the
formatter.
Why: Required for serialising a UCXLAddress back to its textual
representation.
Source§impl FromStr for TemporalAxis
impl FromStr for TemporalAxis
Source§fn from_str(s: &str) -> Result<Self, Self::Err>
fn from_str(s: &str) -> Result<Self, Self::Err>
Parses a temporal axis token from its textual representation.
What: Accepts “#”, “~~” or “^^” and maps them to the corresponding enum variant.
How: A simple match statement is used; an error string is
returned for any unrecognised token.
Why: Centralises validation of temporal markers used throughout the address parsing logic, ensuring consistency.