Step 1: Add Array type handling to WASM backend type system

Co-authored-by: enghitalo <63821277+enghitalo@users.noreply.github.com>

Author: Copilot

vlib/v/gen/wasm/mem.v

@@ -170,7 +170,7 @@ pub fn (mut g Gen) new_local(name string, typ_ ast.Type) Var {
 	// allocate memory, then assign an offset
 	//
 	match ts.info {
-		ast.Struct, ast.ArrayFixed {
+		ast.Struct, ast.ArrayFixed, ast.Array {
 			size, align := g.pool.type_size(typ)
 			padding := calc_padding(g.stack_frame, align)
 			address := g.stack_frame
@@ -289,6 +289,10 @@ pub fn (g &Gen) is_pure_type(typ ast.Type) bool {
 		ast.Enum {
 			return g.is_pure_type(ts.info.typ)
 		}
+		ast.Array {
+			// Dynamic arrays require heap allocation, not pure type
+			return false
+		}
 		else {}
 	}
 	return false

vlib/v/gen/wasm/ops.v

@@ -73,6 +73,10 @@ pub fn (mut g Gen) get_wasm_type(typ_ ast.Type) wasm.ValType {
 		ast.Alias {
 			return g.get_wasm_type(ts.info.parent_type)
 		}
+		ast.Array {
+			// Dynamic arrays are represented as pointer to array struct
+			return wasm.ValType.i32_t // pointer
+		}
 		ast.ArrayFixed {
 			return wasm.ValType.i32_t // pointer
 		}

vlib/v/gen/wasm/tests/step1_array_types.vv

@@ -0,0 +1,10 @@
+// Step 1: Test basic array type handling in WASM backend
+// This verifies that ast.Array types are properly recognized by the type system
+// Actual array initialization and operations will be implemented in later steps
+
+fn main() {
+	println('Step 1: Array type system test')
+	// For now, we're just testing that the WASM backend compiles
+	// with the new Array type handling in get_wasm_type() and is_pure_type()
+	println('Type handling OK')
+}

vlib/v/gen/wasm/tests/step1_array_types.vv.out

@@ -0,0 +1,2 @@
+Step 1: Array type handling test
+Type handling OK