Expand description
Context router for tpt-telos.
Decides, from @boundary(...) architectural metadata, whether a module or
function should be compiled to the Rust backend (CPU-bound, zero-allocation,
cryptographic paths) or the Go backend (network I/O, high-concurrency,
distributed paths).
In Phase 2 only the Rust backend is generated; the router nonetheless records the intended target so the dual-backend work (Phase 3) can consume it without further parsing changes.
Structs§
- Route
- The routing decision for a module or function.
- Routing
Diagnostic - A routing warning emitted when architectural flags imply a potentially unsafe target combination.
Enums§
- Diagnostic
Kind - The kind of routing conflict detected.
- Storage
Class - The storage class for a module’s data structures, derived from
@state(persistent)or@state(ephemeral). - Target
- The compilation backend a module or function is routed to.
Functions§
- route
- Route a module from its own
@boundaryattributes (and any inherited function-level attributes if supplied). Thin wrapper aroundroute_checkedthat discards diagnostics for callers that do not need them. - route_
checked - Route a module from its
@boundaryattributes and emit diagnostics for potentially unsafe target combinations.