2026.05.16.2¶
Two
:record-shape-names:entries for the same set of keys (in any order) now raise a cleanExtensionErrorinstead of silently keeping only the last name.:heterogeneous-strategy:now acceptsauto. It renders the input with its natural representation first – so homogeneous and genuinely map-shaped data keep their native form – and only if that fails because the data is heterogeneous does it retry with each strategy the target language supports, in the order given by the newliteralizer_heterogeneous_strategy_precedenceconfiguration value (default:record,tuple,tagged_enum,object_variant,variant,union_type,interface). This removes the need to pick a single per-project or per-input strategy.Both directives gain a
:skip-if-unrepresentable:flag. When the input cannot be represented in the target language (including afterautoexhausts its precedence), the directive emits no node instead of failing the build, so a per-language loop can skip the languages a given input does not fit without leaking data-shape concerns into prose.A
HeterogeneousCollectionErrorraised by a concrete (non-auto):heterogeneous-strategy:that cannot represent the input is now surfaced as a cleanExtensionErrorrather than an uncaught traceback.