2026.05.17.1

  • ~literalizer.CSharp array sequence-format no longer emits using System; or using System.Collections.Generic;. A C# array literal (new T[] {...}) is a built-in language feature and requires no using directives, so those lines were dead noise on the array path (for example a Dictionary whose values are arrays picked up a spurious using System;). using System.Collections.Generic; is still emitted for the collection types that need it (List<T>, Dictionary<TKey, TValue>, and the set types), and using System; for System scalar types such as DateOnly. The array empty form is now the typed literal new T[] {} rather than Array.Empty<T>(), keeping the array path free of any System reference. See #2524.

  • ~literalizer.literalize_call now accepts a bound_refs argument, the call-side counterpart of ~literalizer.literalize’s own bound_refs. With wrap_in_file=True it renders a complete, self-contained file: each ref is declared (cased via ref_case) ahead of the calls, a no-op stub for the target function is injected, and one reconciled preamble (header and body) is placed in front, so callers no longer hand-roll a duplicate-removal pass. Entries double as ref_values and are emitted in iteration order. Recomputing the body preamble across the union of types and reconciling the data-dependent header block into a single copy covering every type replaces the previous multi-line preamble-filter heuristic. The same single-copy reconciliation now also backs ~literalizer.literalize’s own bound_refs declaration composition, removing the last preamble-filter heuristic there with no change to generated output. See #1946.

  • The supports_call_variable_binding language-class flag has been removed. Every language now binds a ~literalizer.literalize_call result directly with no literal-only wrapping, so the flag was True for all languages and its ~literalizer.exceptions.UnsupportedCallShapeError rejection path was unreachable. No generated output changes. See #2521.