axiolid-dispatch
Provider registration, ordering, fallback, and execution policy.
| Latest release | 0.3.1 (2026-09-28) |
| crates.io | axiolid-dispatch |
| Facade | axiolid feature dispatch-mesh-boolean, dispatch-mesh-section, dispatch-pointcloud-reconstruction |
| Layer | execution (execution.dispatch) |
| API documentation | rustdoc · docs.rs |
| Source | crates/execution/dispatch/ |
Overview
Runtime registries for operation providers: MeshBooleanRegistry, MeshPlaneSectionRegistry and PointcloudReconstructionRegistry, each behind its own feature. A registry owns provider ordering, device matching, fallback to the next provider, and memory-budget admission. It defines no request or result types: those live in the operation-contract crates, and providers implement them without depending on this crate. The parallel feature scopes each dispatched call to a caller-owned CPU pool.
Features
Default: none.
| Feature | Enables |
|---|---|
mesh-boolean | axiolid-core, axiolid-mesh, axiolid-mesh-contracts, axiolid-mesh-boolean-contract |
mesh-section | axiolid-core, axiolid-mesh, axiolid-mesh-contracts, axiolid-mesh-section-contract |
parallel | axiolid-backend-cpu, axiolid-backend-cpu/parallel |
pointcloud-reconstruction | axiolid-pointcloud, axiolid-pointcloud-reconstruction-contract |
Depends on
axiolid-backend-cpuaxiolid-contractsaxiolid-coreaxiolid-meshaxiolid-mesh-boolean-contractaxiolid-mesh-contractsaxiolid-mesh-section-contractaxiolid-pointcloudaxiolid-pointcloud-reconstruction-contract
Changes
Latest release, 0.3.1 (2026-09-28):
Changed
- The crates.io page is this crate's own
README.md, with links to its API documentation, its reference page and the source (ADR 0078).
Full history: crates/execution/dispatch/CHANGELOG.md