Skip to main content

Module root_binding_diagnostics

Module root_binding_diagnostics 

Source
Expand description

Feature-only root-binding boundaries, stored separately from evaluation spans.

These records own bounded name text and scalar diagnostics, never runtime values, scopes, engines or callbacks. A RootAttempt is the first local in bind_root; its final boundary consequently follows later local destruction. Function arguments and the attempt’s own report storage are released later. Name copying happens before the local span starts, but inside its parent.

Like evaluation spans, the counters and clocks are process-wide and include nested work. A cumulative requested peak is not a phase-local peak or RSS. Recording allocates, and parent/child intervals must not be summed together.

When a phase-event sink is installed, a scalar EventScope shares the local span’s ordinal. The local starting stamp precedes the event entry; each mark precedes its next-stage event, and the final mark precedes the ending event. Their clocks therefore bracket different diagnostic recording overhead. Root records retain neither the EventScope nor the event sink.

Structs§

RootAttempt
First-local guard for one root binding, including early return and unwind.
RootRecord
One root attempt, submitted in completion order to this thread’s buffer.

Enums§

Completion
Action actually taken by the root result handler.
Outcome
Result of dispatch, or the final reason an attempt did not return normally.
SourceKind
Source supplied to bind_root, without retaining the source itself.

Constants§

ROOT_NAME_LIMIT
Maximum retained UTF-8 bytes of a root’s diagnostic name.

Functions§

take_root_binding_diagnostics
Drain completed root records without touching evaluation spans or live guards. Ordinals and process counters are not reset. Records retain no runtime owners.