Skip to main content

Crate tpt_telos_router

Crate tpt_telos_router 

Source
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.
RoutingDiagnostic
A routing warning emitted when architectural flags imply a potentially unsafe target combination.

Enums§

DiagnosticKind
The kind of routing conflict detected.
StorageClass
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 @boundary attributes (and any inherited function-level attributes if supplied). Thin wrapper around route_checked that discards diagnostics for callers that do not need them.
route_checked
Route a module from its @boundary attributes and emit diagnostics for potentially unsafe target combinations.