Expand description
Side-effect primitives for async operations.
Reducers are pure functions – they must not perform I/O. When a reducer
needs to trigger a host capability, async job, or runtime-control effect, it
pushes an EffectEnvelope through the Effects builder.
The platform executor fulfils the effect outside the deterministic core and
dispatches the on_ok / on_err callback actions back into the pipeline.
Structs§
- Effect
Envelope - A queued effect with optional success/failure callbacks.
- ReqId
- An opaque request identifier assigned to each emitted effect.
- Resource
Id - An opaque handle to a platform-managed resource (e.g. a large binary blob).
Enums§
- Action
Input - Extra input data passed alongside an action dispatch.
- Effect
- A side-effect emitted by a reducer.
- Runtime
Effect - Runtime-managed effects that are not host capabilities.