A constructor value is written under the key its name is carried under. The key follows the name rather than the type, because that is all a Value carries: Compile.objOf reads it the same way, so the compiler and this write the same object.

encodeValue composed with the crossing at each dictObj position of the declared type.

The declared type is what says how a value leaves the module, and it is the only thing that says it: encodeValue takes no type, so a dictionary encodes to a Map whether or not the author declared it to cross as a plain object. This is what a public declaration's result is read through instead.

The recursion is on sizeOf v rather than on the type, the way Value.hasTy's is: a named type's field types come out of the program, so the Ty need not shrink. Where the value and the type do not line up — which the entry check is what rules out — the value is encoded as it stands.

Where no type the program declares reaches a dictObj and the type reaches none, reading a value through its declared type is reading it without one.

What the three perturbing shapes name, applied to an encoded argument. Reversing an object's keys and giving it a key no type declares are both things the .d.ts admits and encodeValue never writes. A dictionary's keys are left where they are: they are a Map's, and no order is declared for them.

asObject leaves an encoded value alone, because it is not a perturbation of one: encodeArg reads the argument through its declared type instead, and never routes that shape here.

The JavaScript value a vector offers as one argument. Three of the four shapes perturb the canonical encoding and are applied to it; asObject is a second encoding — the argument read through the type it was declared at, which is what writes a Dict.Obj argument as the plain object a consumer would write.

Reshaping an encoded value could not do it. Whether a dictionary crosses as an object is the declared type's to say and an encoded value no longer carries the type, so turning every Map into an object would be refused at a Dict parameter — and the vector says the call returns.

The arguments the generated code is called with: each Value written the way the vector says a caller may write it.

Whether the result of eval and the result of the model are the same. The expected value is read out through the declaration's return type, because that is what the entry hands back — decl_correct says so — and at a dictionary the declared type says crosses as a plain object the two readings differ. Two failures are compared by the thrown code.

Checks that the artifact does not disagree with the reference semantics, before writing it out.

The keys the program declares are installed here, so the compiler and the encoding read one reading — Compile.validateType is what checks that reading against every type the program declares.