2026.05.17¶
Bumped
literalizerto2026.5.17.:variable-name:(with:existing-variable:) onliteralizer-callnow produces a call-result binding forada,bash,c,d,elixir,erlang,forth,fortran,nim,objectivec,systemverilog,tcl, andzig. These languages previously failed the build because they could not bind a call result; they now emit an idiomatic binding (for exampleset my_data [make_widget ...]fortclandauto my_data = make_widget(...);ford), following upstreamliteralizerextendingvariable_formto those languages. No directive change was needed.:heterogeneous-strategy: record(including theautodefault’srecordfallback) and:record-struct-name-prefix:now work forc,csharp,cpp,crystal,d,nim,odin,swift,v, andzig. This follows upstreamliteralizeradding theRECORDstrategy to those languages; the directives expose it generically from the per-language capability flags, so no directive change was needed.:heterogeneous-strategy:now defaults toautoinstead of falling through to literalizer’s per-language default (e.g.errorfor Rust).autorenders the input with its natural representation first – so homogeneous and genuinely map-shaped data render identically to before – and genuinely unrepresentable input still raises, so this only ever turns a representable input that previously broke the build into a representable one. Projects that forcedautoglobally via a directive subclass inconf.pycan drop that override.automakes a representation choice implicitly (recordvstuplevstagged_enumchanges the generated API), so set:heterogeneous-strategy:explicitly – including:heterogeneous-strategy: errorto keep a mixed-scalar collection a hard build failure – when a specific behavior is wanted.The documentation examples now use
sphinx-toolbox’srest-exampledirective, which executes eachliteralizerandliteralizer-calldirective at build time, so the rendered output can no longer drift from the pinnedliteralizerbehavior.