Expand description
Run-scoped state: the value store, the schedulable snapshot RunState, the
node-facing RunContext, and suspension packaging.
The engine owns one trunk RunState per run. It carries the consumer state S
(user), the pin-value store (the dataflow profile’s IO surface), and all activation
accounting — pending tokens, back-edge iteration counters, per-node execution counters,
the current frontier, and the superstep counter. Because all of that lives in one
struct, suspending mid-loop and resuming later is just “stop, keep the struct, continue”
— loop counters continue from where they were, they do not reset.
Structs§
- Pending
Suspension - Single record of a suspended node waiting for external inputs.
- RunContext
- Everything a node may touch, nothing it may not.
- RunState
- The complete schedulable state of one run: consumer state, value store, and all activation accounting. Suspension, resumption, and step-limit results all package this.
- Suspended
Execution - Package containing suspension parameters to resume execution later.
- Value
Store - The engine-owned store of pin values (the dataflow profile’s IO surface).
Enums§
- Engine
Result - Represents the return status of a BSP execution run.