Why Collection mutability tied to let/var in Swift? - Purpose & Use Cases

The Big Idea

What if a simple keyword could save you hours of debugging collection errors?

The Scenario

Imagine you have a list of items you want to update frequently, but you accidentally treat it like a fixed list. You try to add or remove items manually by rewriting the whole list each time.

The Problem

This manual approach is slow and error-prone because you must rewrite the entire list every time you want to change it. It's easy to forget to update parts or accidentally lose data.

The Solution

Swift's collection mutability tied to let and var means if you declare a collection with var, you can change it freely. If you use let, it stays constant. This clear rule helps avoid mistakes and makes your code safer and easier to understand.

Before vs After

✗ Before

let items = ["apple", "banana"]
// To add, create a new list manually
let newItems = items + ["cherry"]

✓ After

var items = ["apple", "banana"]
items.append("cherry")

What It Enables

This concept lets you control when your collections can change, making your code more predictable and less buggy.

Real Life Example

Think of a shopping list app: if the list is declared with var, users can add or remove items easily. If declared with let, the list stays fixed, preventing accidental changes.

Key Takeaways

Using var allows collections to be changed easily.

Using let keeps collections constant and safe.

This rule helps prevent bugs and makes code clearer.