Skip to main content

order_subject_path

Function order_subject_path 

Source
pub fn order_subject_path(
    name: &Ident,
    to_subject_path: &TokenStream,
    subject_path: &TokenStream,
    term_name: &TokenStream,
    columns: &[OrderColumn],
) -> TokenStream
Expand description

THE SAME identity, as the wire’s decode reads it: a PATH rather than one name, and answered through a trait so a decoder generic over the term type can ask.

The arms are built from the same rows order_identity’s are, so the two cannot drift into naming different columns. What differs is the SHAPE and the GATE. The shape is a path because cover.title and title are two subjects and so are cover.title and cover.duration — every emitted term is one segment today, and the path is what keeps the day a term reaches through a relation from being a change to the uniqueness rule. The gate is none: identity is the PAGE’s, where a wire order is every order-capable subject’s.

A const ITEM per arm, and not an inline const { … } block: the block does not make the borrow inside it 'static either, so both spellings without an item are E0716.

match *self rather than match self, and the EMPTY case is what forces it: the trait takes &self, a reference is always considered INHABITED, and an empty match on one is E0004 even where the enum has no variant to write an arm for. Dereferencing puts the match back on the uninhabited place. The populated arm follows the same spelling rather than the reverse, so a subject storing one column and a subject storing none read alike; no arm binds, so nothing moves out of the borrow.