Struct ProcessResult 

pub struct ProcessResult {
    pub output_arrays: Vec<Arc<NDArray>>,
    pub param_updates: Vec<ParamUpdate>,
    pub scatter: bool,
}

Result of processing one array: output arrays + param updates to write back.

Fields

output_arrays: Vec<Arc<NDArray>>

param_updates: Vec<ParamUpdate>

scatter: bool

When true, the output arrays are scattered — delivered to a single downstream consumer in round-robin order rather than broadcast to all. The target consumer (and reroute-past-full / drop-on-last decisions) is owned by the runtime delivery path, which holds the persistent cursor (C++ NDPluginScatter::nextClient_); the processor only marks the frame as a scatter frame.

Implementations

impl ProcessResult

pub fn sink(param_updates: Vec<ParamUpdate>) -> Self

Convenience: sink plugin with only param updates, no output arrays.

pub fn arrays(output_arrays: Vec<Arc<NDArray>>) -> Self

Convenience: passthrough/transform plugin with output arrays but no param updates.

pub fn empty() -> Self

Convenience: no outputs, no param updates.

pub fn scatter(output_arrays: Vec<Arc<NDArray>>) -> Self

Convenience: scatter output — deliver to the next downstream consumer in round-robin order (the runtime owns the cursor and reroute logic).