Kwasm.format.binary.type

From the docs:

Function types are encoded by the byte 0x60 followed by the respective vectors of parameter and result types.

functype    ::= 0x60 rt1:resulttype rt2:resulttype  =>  rt1 → rt2

From the docs:

Global types are encoded by their value type and a flag for their mutability.

globaltype  ::= t:valtype m:mut => m
tmut        ::= 0x00            => const
0x01            => var

From the docs:

Limits are encoded with a preceding flag indicating whether a maximum is present.

limits  ::=     0x00 n:u32          => {min n, max ϵ}
0x01 n:u32 m:u32    => {min n, max m}

From the docs:

Memory types are encoded with their limits.

memtype ::=     lim:limits  =>  lim

From the docs:

Result types are encoded by the respective vectors of value types `.

resulttype   ::= t*:vec(valtype) =>  [t*]

From the docs:

Table types are encoded with their limits and a constant byte indicating their element type.

tabletype   ::=     et:elemtype lim:limits  => lim et
elemtype    ::=     0x70                    => funcref

From the docs:

Value types are encoded by a single byte.

valtype ::= 0x7F    =>  i32
0x7E    =>  i64
0x7D    =>  f32
0x7C    =>  f64

Note

Value types can occur in contexts where type indices are also allowed, such as in the case of block types. Thus, the binary format for types corresponds to the signed LEB128 encoding of small negative sN values, so that they can coexist with (positive) type indices in the future.