type MarkerResult

bendvy-ecs-core@0.1.0.4 · ordinary_machine_handler_bundle.bend:21

import Base
import bendvy-ecs-core@0.1.0.4/world.bend as W
import bendvy-ecs-core@0.1.0.4/system.bend as Sys
import bendvy-ecs-core@0.1.0.4/machine_handlers.bend as H
import bendvy-ecs-core@0.1.0.4/machine_handler_bundle.bend as B
import bendvy-ecs-core@0.1.0.4/schedule.bend as Sch

21# Marker outcome retains the handler bundle and world inside BundleResult,
22# with actual schedule steps and observations. Refusal is distinct from handler
23# failure; use the result status rather than inferring success from step count.
24type MarkerResult<S:Data,K:Data,V:Data,Q:Data,C:Type,R:Type,E:Data,-runner:W.World<S,C,R,E> -> H.Invocation<V> -> Sys.Outcome<W.World<S,C,R,E>,String,Unit>> is Type:
25  MarkerResult{result:B.BundleResult<S,K,V,Q,C,R,E,runner>,steps:List<&2,Sch.Step>,observations:List<&2,Sch.Observation>}