begin sketching out 'collections', which are the formal mechanism in the eval/eval-viz systems for visualizing synthetic structures/arrays/trees produced by the debugger, rather than ad-hocing / hardwiring the correct ev-block production for each kind of view - the views can still stay, but this is an important feature for other cases

src/eval/generated/eval.meta.c

@@ -127,7 +127,7 @@ E_OpInfo e_expr_kind_op_info_table[45] =
 { E_OpKind_Binary, 13, str8_lit_comp(""), str8_lit_comp("="), str8_lit_comp("Define") },
 };
 
-U8 e_kind_basic_byte_size_table[55] =
+U8 e_kind_basic_byte_size_table[56] =
 {
 0,
 0,
@@ -184,9 +184,10 @@ U8 e_kind_basic_byte_size_table[55] =
 0,
 0,
 0,
+0,
 };
 
-String8 e_kind_basic_string_table[55] =
+String8 e_kind_basic_string_table[56] =
 {
 str8_lit_comp(""),
 str8_lit_comp("void"),
@@ -243,6 +244,7 @@ str8_lit_comp("class"),
 str8_lit_comp("enum"),
 str8_lit_comp(""),
 str8_lit_comp(""),
+str8_lit_comp(""),
 };
 
 C_LINKAGE_END