Perform in-place initialization for tuples and structs (#3246)

This implements initializing expression semantics for structs and
tuples, following #2006 and discussions since.

Tuple and (and analogously, struct) literals are treated as having a
mixed expression category that is later resolved based on how the
literal is used, as either a tuple initializer or a tuple value, at
which point we create a `TupleInit` or `TupleValue` that represents the
formation of the tuple initializer or tuple value from the tuple
literal.

There's quite a lot of TODOs here, and the SemIR representation is still
not quite right, but this seems like a good place to checkpoint some
incremental progress.
This commit is contained in:
Richard Smith
2023-09-20 21:20:14 +00:00
committed by GitHub
parent f747cb0c93
commit 842b471e67
71 changed files with 904 additions and 533 deletions
+2 -9
View File
@@ -22,13 +22,6 @@ fn G() -> i32 {
// CHECK:STDOUT: }
// CHECK:STDOUT:
// CHECK:STDOUT: define i32 @G() {
// CHECK:STDOUT: %tuple = alloca { i32, i32, i32 }, align 8
// CHECK:STDOUT: %1 = getelementptr inbounds { i32, i32, i32 }, ptr %tuple, i32 0, i32 0
// CHECK:STDOUT: store i32 1, ptr %1, align 4
// CHECK:STDOUT: %2 = getelementptr inbounds { i32, i32, i32 }, ptr %tuple, i32 0, i32 1
// CHECK:STDOUT: store i32 2, ptr %2, align 4
// CHECK:STDOUT: %3 = getelementptr inbounds { i32, i32, i32 }, ptr %tuple, i32 0, i32 2
// CHECK:STDOUT: store i32 3, ptr %3, align 4
// CHECK:STDOUT: %temp = alloca [3 x i32], align 4
// CHECK:STDOUT: %array.index = getelementptr inbounds [3 x i32], ptr %temp, i32 0, i32 0
// CHECK:STDOUT: store i32 1, ptr %array.index, align 4
@@ -39,6 +32,6 @@ fn G() -> i32 {
// CHECK:STDOUT: %F = call i32 @F(ptr %temp, i32 1)
// CHECK:STDOUT: %temp3 = alloca i32, align 4
// CHECK:STDOUT: store i32 %F, ptr %temp3, align 4
// CHECK:STDOUT: %4 = load i32, ptr %temp3, align 4
// CHECK:STDOUT: ret i32 %4
// CHECK:STDOUT: %1 = load i32, ptr %temp3, align 4
// CHECK:STDOUT: ret i32 %1
// CHECK:STDOUT: }