Module encode 

One value, one type, the bytes between them — at serde_json::Value.

The walk is zerodds_wire_codec::encode’s and follows the layout plan, not a second reading of the model. What is here is the value file’s end of it: the three entry points pinned to the representation the probe reads, and the front end that turns IDL text into the model they take — which is the probe’s business and not the engine’s, so zerodds-wire-codec names no parser.

The three carry a recursion marker for the reason contract.rs’s module note gives: dds_bounded_recursion reads a path call by its last segment, so forwarding to the function of the same name in the other crate looks like recursion. Depth 1 each.

Enums

ProbeError

Why a probe could not produce bytes.

Functions

encode

Serialise values as request.type_name. See zerodds_wire_codec::encode::encode.

encode_recording

As encode, recording which scalars of the value were read. See zerodds_wire_codec::encode::encode_recording.

encode_with_padding

As encode, and the offsets of the octets that carry no value. See zerodds_wire_codec::encode::encode_with_padding.

hex

The bytes as lowercase hex, which is how the fixtures record them.

model_from_idl

Parse and lower one IDL source into a model with everything resolved, which is what a probe needs before it can plan anything.

model_from_idl_in_dialect

The same model, lowered under one dialect’s front-end answers.

model_from_idl_with

The same model, with every front-end option spelled out.

probe

Shorthand for the common case: one IDL source, one type, one value.