Struct BehaviorSystem 

pub struct BehaviorSystem { /* private fields */ }

Runs a world’s Behavior components: their firing rules, their bodies, and the effects those produce.

new evaluates every run on the calling thread and persists nothing; a host lends it a thread pool through with_scheduler and somewhere to keep state through with_store.

Implementations

impl BehaviorSystem

pub fn new() -> Self

A system that evaluates serially and persists nothing.

pub fn with_store(self, store: Box<dyn BehaviorStore>) -> Self

Keep this world’s variables and once flags in store.

pub fn with_scheduler(self, scheduler: Box<dyn EvalScheduler>) -> Self

Fan a tick’s evaluation out through scheduler once enough instances fire at once to pay for it.

Trait Implementations

impl Debug for BehaviorSystem

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for BehaviorSystem

fn default() -> BehaviorSystem

Returns the “default value” for a type.

impl System for BehaviorSystem

fn init(&mut self, ctx: &mut PipelineContext<'_>)

Run once at World::start, before the first step.

fn step(&mut self, ctx: &mut PipelineContext<'_>) -> StepResult

Run once per tick.

fn access(&self) -> Access

The data step may touch, consulted once when the schedule is built (after init, so a data-dependent system can compute it from its compiled state). The default claims everything: an undeclared system is ordered against all others and never runs concurrently, which is always safe. Declaring narrower access is what admits a system to shared waves and to debug-build access validation.