pub enum Shape {
Path(Vec<Column>),
Kinds(Vec<Kind>),
}Expand description
The two things a lineage can BE, and therefore the two types that can be emitted for one.
The split is the topology’s, not a convenience: a node with one ancestry has a PATH, and every row of it carries the same columns; a node drawing from several independent upstreams has a CHOICE, and which columns a row carries depends on which upstream it came from. A struct with nullable columns would express the second, and would make the invalid states representable — which is the whole reason the storage layout beneath it splits too.
Variants§
Path(Vec<Column>)
A PATH: one column per step, root-first, as a struct. Never empty — an empty path is a root,
and a root has no Lineage at all.
Kinds(Vec<Kind>)
A CHOICE: one variant per upstream, each carrying that upstream’s whole key, as an enum.
Trait Implementations§
Auto Trait Implementations§
impl !Send for Shape
impl !Sync for Shape
impl Freeze for Shape
impl RefUnwindSafe for Shape
impl Unpin for Shape
impl UnsafeUnpin for Shape
impl UnwindSafe for Shape
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more