Expand description
The sans-IO Engine state machine. The sans-IO Engine state machine
Re-exports§
pub use bootstrap::BootstrapKind;pub use bootstrap::BootstrapRequest;pub use bootstrap::BootstrapStatus;pub use bootstrap::ComponentBootstrap;pub use bootstrap::InFlightBootstrap;pub use bootstrap::ModuleBootstrap;pub use bootstrap::OwnedBootstrapRequest;pub use bootstrap::QueuedBootstrap;pub use bootstrap::ReadyBootstrap;pub use core::Engine;pub use core::EngineStats;pub use dispatch_entry::OpDispatch;pub use dispatch_entry::StatelessInvokeFn;pub use graph_slot::GraphSlot;pub use invoke::make_protocol_dispatcher;pub use pending_async::ExecutionState;pub use pending_async::PendingAsync;pub use step::EngineStep;
Modules§
- bootstrap
- Engine bootstrap state — consolidated owner of every bootstrap field the engine reads during install + poll.
- call_
context - Per-function-call invocation context.
- core
- The
Enginestruct + test-only constructor + registration accessors. Hot-path poll cycle lives inengine::poll. - dispatch_
entry - Engine dispatch types
- graph_
slot GraphSlot- per-FunctionProto compiled data perdocs/ENGINE.md§3.- invoke
- Op invocation lifecycle
- pending_
async PendingAsync+ExecutionState- engine’s async-suspension bookkeeping + execution liveness tracking per §5.3.- poll
- 8-phase poll cycle +
handle_completionperdocs/ENGINE.md§7 + §9. - step
EngineStep- observable output ofEngine::pollperdocs/ENGINE.md§10 +docs/internal/IMPLEMENTATION_PLAN.md//! lines 751-753.