pub enum Stage {
Annotate,
Expand,
Route,
}Expand description
WHERE A FAN SEGMENT SITS IN THE PIPELINE’S OWN ORDER — the ②-before-④ opinion, as data.
The framework owns this opinion now. A question is WIDENED before it is CROSSED, because the crossing turns a question into probes and a widening is an endomorphism over questions: an expansion after a routing would have to widen a probe, which is a different type in a different currency, chosen by whatever store the lane belongs to.
It is Ord BY DECLARATION ORDER, which is what makes the rule a comparison rather than a pair
of hand-written arms — and what makes the next stage one variant rather than a rewrite. The
resident-hop word the closed design records as stage ⟂ arrived exactly that way: one variant
BEFORE Expand, and not one line of the check that reads this enum moved.
Variants§
Annotate
⟂ — the question is ANNOTATED: one question in, THE SAME question out, one fact richer.
Expand
② — the question WIDENS: one question in, several questions of the same type out.
Route
④ — the question CROSSES: one question in, one probe per lane out.
Implementations§
Source§impl Stage
impl Stage
Sourcepub const fn word(self) -> &'static str
pub const fn word(self) -> &'static str
The WORD a declaration opens this stage with.
Here rather than on Fan, because a refusal about the ORDER names a stage it has no fan in
hand for: the check reads stages, and a sentence that hard-coded two spellings would start
lying the round a third stage arrives.
Sourcepub const fn why_first(self) -> &'static str
pub const fn why_first(self) -> &'static str
WHY THIS STAGE RUNS WHERE IT DOES — the clause an out-of-order refusal quotes.
It hangs on the stage that was written LATE rather than on the pair, because that is what the
reason is a fact about: a widening comes before a crossing because of what a WIDENING is, and
an annotation comes before both because of what stages READ. A per-pair table would be n²
sentences for a rule that has n.