Expand description
Supply infrastructure for variable relationship tracking.
Supplies provide efficient access to derived information about planning variables, such as inverse relationships (who points to whom) and anchor tracking (chain roots).
The supply pattern enables O(1) lookups that would otherwise require O(n) scans.
§Architecture
Supply: Marker trait for all supply typesSupplyDemand: Request a specific supply type from the managerSupplyManager: Registry holding all active suppliesListVariableStateSupply: Centralized tracking for list variable shadow state
Structs§
- Anchor
Variable Demand - Demand for an anchor variable supply.
- Demand
Key - A unique key identifying a supply demand.
- Externalized
Anchor Variable Supply - Hash-based implementation of anchor variable supply.
- Externalized
Singleton Inverse Variable Supply - Hash-based implementation of inverse variable supply.
- List
Variable State Demand - Demand for a ListVariableStateSupply.
- List
Variable State Supply - Supply that tracks list variable element positions.
- Singleton
Inverse Variable Demand - Demand for a singleton inverse variable supply.
- Supply
Manager - Manager that holds and provides supplies.
Enums§
- Element
Position - Position of an element within a list variable.
Traits§
- Anchor
Variable Supply - Supply that provides O(1) lookup of an entity’s chain anchor.
- Index
Variable Supply - Trait for supplies that provide index information.
- Inverse
Variable Supply - Trait for supplies that provide inverse (owner entity) information.
- Singleton
Inverse Variable Supply - Supply that provides O(1) lookup of the entity pointing to a value.
- Supply
- Marker trait for all supply types.
- Supply
Demand - Trait for requesting a specific type of supply.