Targets · Dart · Example
The whole language in one short program — a module with a record, a tagged union, a function with per-platform native bodies, and a function that wires up state, a write-back and a return — and the complete Dart it renders to. It is the same program shown on the language page .
How a Program becomes Dart, in parts. Start with the introduction, then follow each part into the rendered output and the runtime it links against.
Each keyword has its own page under keywords ; here they are all together.
The record and union become final classes named by the underscore join; the module's functions are statics on a class; state carries an explicit type; the function's dart body is spliced in; and the trailing = becomes a return .
Indentation becomes nested closures — the REVERSE body is a trailing () { … } . Dotted names are joined with an underscore, keeping the final access a real dot ( Maths_Integer.ToString ) — see naming considerations . The per-keyword mapping is on keywords .