~literalizer.Rust gains the TUPLE heterogeneous_strategy.
A fixed-length heterogeneous scalar array that is a dict value, a record field value, or the document root (every element scalar, spanning at least two scalar buckets) is rendered as a native tuple (e0, e1, ...) typed (T0, T1, ...) instead of raising.
It composes with RECORD: a record field whose value is such an array becomes a tuple-typed struct field.
Heterogeneous arrays nested inside another list, or containing a non-scalar element, stay out of scope and still raise.
This lands the shared, language-agnostic machinery with Rust as the reference implementation; one language port follows per PR.
See #2327.
~literalizer.literalize_call’s zip_values parameter is replaced by a zip_source / zip_input_format pair, mirroring the primary source / input_format.
zip_source is parsed internally with the same parser as source (so YAML !!omap, datetime/bytes coercion, JSON5, TOML, … behave identically by construction); its parsed top-level elements pair positionally with the generated calls (element-by-element when per_element is True, otherwise the whole parsed value pairs with the single call) and are surfaced on ~literalizer.CallContext.zipped exactly as before.
Callers no longer need to parse a companion file themselves or reach into private parsing internals.
Supplying zip_source without zip_input_format raises the new ~literalizer.exceptions.ZipSourceWithoutInputFormatError; the existing ~literalizer.exceptions.ZipValuesWithoutCallTransformError and ~literalizer.exceptions.ZipValuesLengthMismatchError contracts are unchanged, and a per_element=True zip_source that does not parse to a list raises ~literalizer.exceptions.PerElementNotListError.
See #2340.
~literalizer.Go gains the record_shape_names constructor parameter (already on ~literalizer.Rust), a Mapping[frozenset[str], str] from a record shape’s key-set to a custom struct name.
A mapped shape is declared and rendered with the given name instead of the auto-generated RecordN; the record_struct_name_prefix counter advances only for the shapes with no custom name.
Names are validated as PascalCase Go identifiers that do not collide with the auto {prefix}{N} pattern or each other, raising ~literalizer.exceptions.InvalidRecordNameError.
A new supports_record_shape_names language-class flag mirrors the constructor.
See #2324.
~literalizer.Kotlin gains the same record_shape_names constructor parameter, a Mapping[frozenset[str], str] from a record shape’s key-set to a custom data class name.
A mapped shape is declared and rendered with the given name instead of the auto-generated RecordN; the record_struct_name_prefix counter advances only for the shapes with no custom name.
Names are validated as PascalCase Kotlin identifiers that do not collide with the auto {prefix}{N} pattern or each other, raising ~literalizer.exceptions.InvalidRecordNameError.
Its supports_record_shape_names language-class flag is now True.
See #2324.
~literalizer.Kotlin now declares a data class field whose value is a custom-named nested record with that nested record’s record_shape_names name (e.g. Entry).
Previously such a field fell through to Double because the custom name does not match the auto-generated {prefix}{N} head, so the generated Kotlin did not compile.
See #2348.