v0.29.0—Sharper bug analysis, reliable resource cleanup, and stronger test and CI checks.See what's new

calor feature-check

Check whether the C#-to-Calor converter supports a C# feature.

Bash
calor feature-check async-await
calor feature-check --list
calor feature-check --list --level partial

--level filters the registry to full, partial, notsupported, or manualrequired. The command always prints a schema 2.0 envelope with the answer under data: supportLevel, description, and an alternative. A name that is not in the registry returns "found": false.

A support level describes the converter's expected handling, not a guarantee for your file. Conversion can still preserve an unsupported construct as an interop block. Use calor coverage for a source-file-specific report and calor convert for the actual conversion and loss report. Most feature names in a conversion report, such as iterator-accessor, are registry names you can pass to this command. A few are labels for a preservation mechanism, not features: post-validation-fallback (a rescue or passthrough) returns "found": false.

Interop Features in 0.25

These are the registry entries for the C# features the interoperability guide covers, as the 0.25 converter (not yet released) reports them. Partial means some shapes convert natively and the rest stay C#; the description lists which.

FeatureLevelNativeStays C#
ref-parameterPartialref parameters and §A{ref} argumentsref locals and returns, conditional refs, scoped/ref readonly, by-reference delegates, constructor and indexer arguments, method-generic by-reference parameters
out-parameterPartialout parameters and §A{out} arguments, out _; flow attributes such as [NotNullWhen] are copied but inertmethod-generic out T
out-varPartialout var in an expression statement, local declaration, return, or if condition directly in a blockchained assignments, a visible default member, loop/using/lock headers, lambdas, queries, holes, filters, initializers, expression-bodied members
in-parameterFullin parameters and §A{in} argumentscall sites that omit in, pass a value, or pass an operand that runs code (the statement stays C#), and in indexer parameters
string-interpolationPartialstring/object targets; FormattableString/IFormattable targets with holeshandler targets, hole-free FormattableString targets, holes outside the native subset
string-interpolation-to-stringFullstring/object targets—
string-interpolation-formattablePartialtargets with at least one hole, via an explicit casthole-free targets
string-interpolation-holePartialnames; regular string, char, bool and int literals; plain-digit double literals with a fractional part; dotted member access; operators over those (not as, is or ??); nameof; typeof; dotted calls with positional arguments of those kinds (not null, and member access only on a name)other holes, including decimal, long and whole-number double literals and operators with a call operand, keep their C# text as §CS{...}
string-interpolation-handlerNotSupported—the statement or member
local-functionPartialthe bounded slice in the guide: non-capturing, declared directly in a method body, plain by-value parameters, used only as a call or in a checked value positionany other local function (the whole member stays C#)
iterator-accessorNotSupported—the property or indexer (§CSHARP)
partial-propertyNotSupported—each declaration (§CSHARP)
array-element-blockNotSupported—the statement holding a collection-initializer element, or a multi-line element in a rectangular array row

Known gaps between the registry and 0.25 behavior. One remains; trust the conversion report:

  • yield-return is Full for iterator methods only. Iterator accessors are iterator-accessor (NotSupported).

Collection Expressions and Patterns in 0.27

The unreleased 0.27 converter preserves more collection expressions and patterns as C#. This avoids changing runtime collection types, enumeration order, matching or binding. The registry entries describe these limits:

FeatureLevelNativeStays C#
collection-expressionPartialarray targets without spreads; the single-spread case belowother collection targets, to retain their runtime type
collection-spreadPartiala single array spread into an array targetother spreads, to retain enumeration order
collection-spread-mixedPartial—mixed spreads, to retain enumeration and element evaluation order
complex-is-patternPartialsimple is checks and declaration patternsproperty and positional patterns, and other complex checks whose lowering could change evaluation or binding