From 85e5acf7669985797f37b60fd2f9e9f4e31a8d78 Mon Sep 17 00:00:00 2001 From: bkchr Date: Fri, 8 Mar 2024 00:48:56 +0000 Subject: [PATCH] deploy: 99e179cbc1432b7a3655d40b940cbdde92ed016d --- print.html | 2 +- proposed/0078-merkleized-metadata.html | 2 +- searchindex.js | 2 +- searchindex.json | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/print.html b/print.html index c871a1f..709cc93 100644 --- a/print.html +++ b/print.html @@ -2623,7 +2623,7 @@ enum TypeRef {

Every Type is composed of multiple different types. Each of these "sub types" can reference either a full Type again or reference one of the primitive types. This is where TypeRef becomes relevant as the type referencing information. To reference a Type in the type information, a unique identifier is used. As primitive types can be represented using a single byte, they are not put as separate types into the type information. Instead the primitive types are directly part of TypeRef to not require the overhead of referencing them in an extra Type. The special primitive type Void represents a type that encodes to nothing and can be decoded from nothing. As FRAME doesn't support Compact as primitive type it requires a more involved implementation to convert a FRAME type to a Compact primitive type. SCALE only supports u8, u16, u32, u64 and u128 as Compact which maps onto the primitive type declaration in the RFC. One special case is a Compact that wraps an empty Tuple which is expressed as primitive type Void.

The TypeDef variants have the following meaning: