2026.05.15.1

  • ~literalizer.Java gains the RECORD heterogeneous_strategy (already on ~literalizer.Rust and ~literalizer.Go). Each record-shaped dict (non-empty, string-keyed) becomes a generated top-level record RecordN(type field, ...) {} declaration plus a matching positional new RecordN(value, ...) literal, so a dict whose values mix scalars and containers is representable instead of raising. Component names keep the original keys and the record-name prefix is configurable via the new record_struct_name_prefix constructor parameter. Generated record declarations require Java 16, so a RECORD spec pins language_version to JDK_16. See #2300.

  • ~literalizer.literalize_call’s call_transform now receives a ~literalizer.CallContext instead of the bare call string. The context exposes call (the rendered call expression, formerly the sole argument), the zero-based index, the input row, and zipped. A new zip_values parameter pairs a second, equal-length sequence positionally with the generated calls; each entry is rendered as a language-native literal and surfaced on ~literalizer.CallContext.zipped, so a transform can print an expected value beside each call’s actual return value. zip_values requires a call_transform and must match the call count, raising the new ~literalizer.exceptions.ZipValuesWithoutCallTransformError / ~literalizer.exceptions.ZipValuesLengthMismatchError. call_transform is now supported only for call styles whose form is an expression that can be wrapped (positional, keyword, object); the sentinel-probe wrapper synthesis for prefix/postfix/command styles has been removed, and those styles now reject call_transform with ~literalizer.exceptions.UnsupportedCallShapeError. ~literalizer.literalize_call no longer raises DottedCallStubNotSupportedError or FreeFunctionCallNotSupportedError (a context-aware call_transform is opaque, so the core cannot inspect the wrapper); those exceptions are removed. The supports_dotted_call_stub / has_free_function_calls language attributes are retained as descriptive metadata for callers that generate wrapper stubs. See #2293.

  • ~literalizer.Kotlin gains the RECORD heterogeneous_strategy (already on ~literalizer.Rust and ~literalizer.Go). Each record-shaped dict (non-empty, string-keyed) becomes a generated data class RecordN(val ...) declared in the preamble plus a matching RecordN(field = value, ...) literal, so a dict whose values mix scalars and containers is representable instead of raising. Field names keep the original dict keys and the data-class-name prefix is configurable via the new record_struct_name_prefix constructor parameter. See #2298.

  • ~literalizer._language.LanguageCls now exposes a supports_record_struct_name_prefix flag alongside the existing supports_* family. Runtime-dispatched callers that look up a language by name can use it to decide whether to pass the record_struct_name_prefix constructor keyword argument without inspecting dataclass fields or the __init__ signature. It is True on ~literalizer.Go, ~literalizer.Kotlin, and ~literalizer.Rust, and False on every other language.

  • ~literalizer.Java now offers VersionFormats.JDK_16 alongside VersionFormats.JDK_11 (still the default), selected via language_version. Generated code is currently identical for both targets; the member exists so a future Java RECORD heterogeneous_strategy (whose record declarations require Java 16) can gate on it. The golden harness emits a parallel @jdk_16 fixture set. See #2313.