Struct RunContext 

pub struct RunContext { /* private fields */ }

Per-unit run context — the Rust mirror of Python’s ContextManager for the typed-channel concern.

All mutable state lives behind Mutex so the dispatch functions can be called from a multi-threaded executor. Arc<TypedEventBus> because the bus itself is already internally synchronised.

Implementations

impl RunContext

pub fn new(bus: Arc<TypedEventBus>) -> Self

Wrap an existing bus in a fresh context.

pub fn bus(&self) -> &TypedEventBus

pub fn from_ir_program(ir: &IRProgram) -> Self

Bootstrap a context from an IRProgram. Every IRChannel is registered on a fresh TypedEventBus whose registry is the canonical source for typed handles during the run.

pub fn set_variable(&self, name: impl Into<String>, value: RunValue)

pub fn get_variable(&self, name: &str) -> Option<RunValue>

pub fn set_step_result(&self, name: impl Into<String>, value: RunValue)

pub fn get_step_result(&self, name: &str) -> Option<RunValue>

pub fn bind_discovered_handle( &self, alias: impl Into<String>, handle: TypedChannelHandle, )

pub fn discovered_handles_snapshot(&self) -> HashMap<String, TypedChannelHandle>

pub fn record_capability(&self, channel: impl Into<String>, cap: Capability)

pub fn take_capability(&self, channel: &str) -> Option<Capability>

pub fn resolve_value_ref( &self, value_ref: &str, ) -> Result<RunValue, DispatchError>

Resolve an emit value_ref against the live state.

Lookup order #1 → #3, walking nested segments after dots:

1. discovered_handles[head]
2. variables[head]
3. step_results[head]

On dotted paths, after the head the remaining segments walk either:

• JSON object access (Json),
• struct-like field access on the handle struct (very few fields; we expose the same surface the Python getattr reaches on a TypedChannelHandle — name, message, qos, lifetime, persistence, shield_ref).