2026.05.14¶
Bumped
literalizerto2026.5.14.1.UnrepresentableInputErrorfromliteralizer(raised when a YAML input contains a non-string dict key that the target language cannot represent) is now surfaced as a SphinxExtensionErrorrather than an uncaught traceback.The
literalizer-calldirective now accepts:variable-name:,:existing-variable:, and:modifiers:options, wrapping the rendered call in an idiomatic per-language variable binding (e.g.let my_data = make_widget(42);).:both-variable-forms:is not supported forliteralizer-callbecause emitting both a declaration and an assignment would invoke the target function twice; upstreamliteralizerraisesUnsupportedCallShapeErrorfor languages whose call form is a statement rather than an expression, or whose declaration template is only valid for literal values.Removed the
:line-ending:directive option. Upstreamliteralizerremoved the correspondingLineEndingsenum; statement terminators now follow each language’s idiomatic default.Languages whose
wrap_in_fileintroduces a named scope (e.g. Java, C, C++, D, Erlang, Fortran, F#, Objective-C, Occam, SystemVerilog) now require:variable-name:when:wrap-in-file:is set. UpstreamliteralizerraisesWrapInFileWithoutVariableNotSupportedErrorfor languages that cannot represent a bare value at file-statement scope.The
:variable-type-hints:option exposes upstream’s newsafevalue, and the previousautovalue is now spellednever(the rendered output is unchanged for languages that did not previously distinguish the two).The
:call-style:option exposes the newcurriedvalue for F#, Haskell, OCaml, and SML. Elmliteralizer-calloutput now emits curried-application calls in place of the prior tuple form.The new upstream typed exceptions raised by directive option combinations a language cannot represent (
WrapInFileWithoutVariableNotSupportedError,WrapCombinedInFileNotSupportedError,VariableNameNotSupportedError,UnsupportedCallShapeError,UnsupportedIdentifierCaseError,DottedCallTargetNotSupportedError,DottedCallStubNotSupportedError,FreeFunctionCallNotSupportedError, andCallArgNotSupportedError) are now caught and re-raised asExtensionErrorso the offending directive is reported as a build error rather than a traceback.