Merge Streams

1 Version

Fans several same-typed input streams t into one output of the same type, interleaving each value as it fires. Values pass through unchanged; this is a merge via merge_streams, not a join — inputs are not paired or zipped.

How it fits

Typical backends

Aggregate several audio sources into one transcription stage.

Combine multiple alarm sources into a single JSON egress.

Fan replicated stage outputs back into one consumer, then log them.

Caveats

Hard constraintAll inputs must share the same type t; merging differently-typed sources belongs in pack_union / unpack_union.
I/O contractNo ordering guarantee beyond arrival order; values from different inputs that fire on the same tick resolve non-deterministically.
LatencyOutput cadence is the combined rate of all inputs, so downstream must tolerate the summed throughput.
I/O contractThis is a fan-in, not a join: each value is forwarded unchanged and inputs are never paired or zipped.

Versions

e9f887d2defaultlatestTransformation
10/12/2023