2026.05.17.1¶
The error raised for an unrecognized
:modifiers:value is now'<value>' is not a valid value. Choose from: ...(listing the modifiers the target language supports), replacing the previousLanguage '<name>' does not support modifier '<value>'.message. A single shared helper now converts these string options to their internal values and raises a cleanExtensionErrorinstead of relying on each option’s input validator to constrain the value.Bumped
literalizerto2026.5.17.1.:wrap-in-file:is now honored by theliteralizer-calldirective. It was previously parsed (and documented as a shared option) but silently ignored, soliteralizer-callalways emitted bare calls. It now passeswrap_in_filethrough toliteralize_call, which upstream2026.5.17.1extended to render a complete, self-contained file: an injected no-op stub for the target function (and any declared refs) precedes the generated calls, with a single reconciled preamble.C# array sequence-format output no longer carries a spurious
using System;/using System.Collections.Generic;line, and the empty array form is now the typed literalnew T[] {}rather thanArray.Empty<T>(), following upstreamliteralizer2026.5.17.1. No directive change was needed; rendered C# array examples update automatically.