Pack Tuple

1 Version

Packs N positional input streams, each carrying a type $pack_types, into a single tuple ($pack_types...), preserving wiring order with each element's type kept verbatim and no field names. Inverse of unpack_tuple.

How it fits

Typical backends

Bundle two independent streams into a positional tuple for a joint consumer that serialises them to JSON.

Pair a count with a payload, then drive a counted replication burst.

Caveats

Hard constraintAll input streams must tick together; the slowest input throttles the tuple and a missing element stalls the pack for that tick.
I/O contractTuples are positional; downstream readers depend on the exact wiring order, so reordering inputs is a breaking change.
LatencyOutput cadence equals the slowest input cadence by construction.
I/O contractFor field-named access use pack_record instead.

Versions

292cf301latestdefaultTransformation
7/20/2022