Languages

What Comline supports in each target language. Every language has its own page, with what its code generator emits and what its runtime speaks on the wire. The matrices below compare the languages side by side.

Nothing here is written by hand. Each entry comes from a conformance suite, which checks the claim against what the generator actually does, so a language page can't claim something that isn't true.

What the states mean

A runtime's claims use the same words, about the wire:

How a claim is proven

Each generator states its support in a SUPPORT table in its own crate. The conformance suite in ComlineProject/generation runs every generator over a corpus of schemas and checks each claim against what the generator actually does:

• supported or partial: a schema in the corpus uses the feature, generates, and matches its checked-in output. Where the feature can be taken out of the schema, the output must change without it; otherwise the feature is really being ignored.
• ignored: the output is identical with the feature taken out, apart from the IR hash, which names the schema.
• unsupported: every schema using the feature is refused, with an error naming the feature.

A claim that no schema in the corpus can back fails the suite. So a new feature, or a generator that gains one, comes with a schema that proves it. The proving schemas are named in each cell below.

Runtimes are proven against a shared wire corpus in ComlineProject/runtime: for each wire feature, examples of exact bytes and the input that produces them, plus bytes that must be refused. The Rust runtime is the reference that the examples are taken from; every other runtime vendors them at a pinned commit. A runtime's suite runs every example against it:

• supported: every example encodes to its bytes and decodes back, and every malformed one is refused. JSON compares as JSON, with numbers exact, so 1 and 1.0 are equal but a rounded large integer isn't.
• partial: as for supported, except for the listed examples, which must still fail. When one starts passing, the suite fails until the claim is upgraded.
• unsupported: the runtime reports every example as not implemented.

Code generation, side by side

Runtimes, side by side

Elsewhere

• comline targets --features prints the code generation support for the generators your comline was built with, and --json prints it as JSON (see the CLI).
• In the editor, a schema using a feature that a language declared in config.idp can't generate gets a warning at the use. Hovering the language in config.idp shows what its generator supports.
• Each generator's repository README carries its own table: comline-rust, comline-typescript.