Skip to main content

columns

Function columns 

Source
pub fn columns(root: &Type, krate: &Path) -> FieldsNamed
Expand description

The four canonical columns, minted whole — the ONE authority for a mounted journal’s shape.

Handed back as a declaration’s own field list, markers and all, because that is what the record pass reads: the front end swaps them into the host it was given and every rule downstream is the rule that was already there. Nothing about the shape is decided twice.

The four columns are the SAME four whether or not the journal named a store, which is the participation inversion read from the mint’s side.

The root column used to carry a bare #[ingraph(persist)] and the other three used to carry one beside their own word, both only where a storage block had been written — because the marker was what put a column in the row. Data fields ARE the row now, so a marker that says so is a word nobody reads, and the branch that wrote it is gone with it. WHICH RUNG the mount lands on is the front end’s, decided from the store words and spent as the node kind it parses under; nothing about the column list depends on it.

The KEY-side columns (root and node) carry no family label and cannot: a label on a key column is refused by the record grammar, the key’s own crossing being decided by its type.