Why collections are value types in Swift - Visual Breakdown

Concept Flow - Why collections are value types in Swift

Create Collection

↓

Assign to Variable A

↓

Copy to Variable B

↓

Modify B

↓

Check A and B

↓

A unchanged, B changed

↓

Value Type Behavior Confirmed

This flow shows how creating and copying collections in Swift leads to independent copies, demonstrating value type behavior.

Execution Sample

Swift

var arrayA = [1, 2, 3]
var arrayB = arrayA
arrayB.append(4)
print(arrayA)
print(arrayB)

This code copies an array and modifies the copy, showing the original stays unchanged.

Execution Table

Step	Action	arrayA	arrayB	Output
1	Create arrayA with [1, 2, 3]	[1, 2, 3]	nil
2	Copy arrayA to arrayB	[1, 2, 3]	[1, 2, 3]
3	Append 4 to arrayB	[1, 2, 3]	[1, 2, 3, 4]
4	Print arrayA	[1, 2, 3]	[1, 2, 3, 4]	[1, 2, 3]
5	Print arrayB	[1, 2, 3]	[1, 2, 3, 4]	[1, 2, 3, 4]

💡 arrayB modified independently; arrayA remains unchanged, confirming value type behavior.

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
arrayA	nil	[1, 2, 3]	[1, 2, 3]	[1, 2, 3]	[1, 2, 3]
arrayB	nil	nil	[1, 2, 3]	[1, 2, 3, 4]	[1, 2, 3, 4]

Key Moments - 2 Insights

Why does modifying arrayB not change arrayA?

Because arrays in Swift are value types, copying arrayA to arrayB creates a new independent copy. Modifying arrayB affects only that copy, as shown in execution_table rows 3 and 4.

Is the copy of the array immediate or delayed?

Swift uses copy-on-write optimization, so the actual copy happens only when arrayB is modified (row 3). Before that, both variables share storage but behave as separate values.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of arrayA after step 3?

A [1, 2, 3]

B [1, 2, 3, 4]

C nil

D []

💡 Hint

Check the 'arrayA' column at step 3 in the execution_table.

At which step does arrayB change independently from arrayA?

A Step 2

B Step 3

C Step 4

D Step 1

💡 Hint

Look at the 'Action' and 'arrayB' columns in execution_table rows.

If Swift collections were reference types, what would happen after modifying arrayB?

A Only arrayB would change

B Neither would change

C arrayA and arrayB would both change

D arrayA would be deleted

💡 Hint

Think about how reference types share the same data, unlike value types shown in variable_tracker.

Concept Snapshot

Swift collections like arrays are value types.
Assigning copies the data, not just the reference.
Modifying one copy does not affect others.
Swift uses copy-on-write for efficiency.
This ensures safety and predictability in code.

Full Transcript

In Swift, collections such as arrays are value types. When you assign an array to a new variable, Swift creates a copy of the data. This means if you change the new array, the original stays the same. The code example shows creating arrayA, copying it to arrayB, then modifying arrayB. The output confirms arrayA is unchanged. Swift optimizes this with copy-on-write, delaying the actual copy until modification. This behavior helps avoid unexpected changes and makes code safer and easier to understand.