Swift version: 5.2
Swift developers rely heavily on constants rather than variables, to the point where Xcode even warns you if you create a variable then never change it. There are three main reasons why immutability is important in Swift, and I want to walk through them briefly.
First, immutability makes your code easier to reason about. If you use constants everywhere, you know for sure that your data can’t be changed by surprise by some other part of your program – in fact, it can’t be changed at all. This also makes multi-threaded code significantly easier to think about.
Second, it stops you making silly mistakes. When you use a constant rather than a variable, Swift won’t let you change that constant no matter how hard you try – it’s like you’ve made a contract with yourself.
Third, Swift can optimize it more efficiently. If Swift knows a value can’t be changed, it can in theory store your data in a more efficient way.
SPONSORED Catch bugs as soon as they happen and know exactly why a crash occurred. Instabug's SDK grabs all the logs they need to fix bugs, crashes and performance issues in minutes instead of days. Get screenshots, device details, network logs, repro steps, and tons of other critical insights needed to resolve issues and prioritize product backlogs straight from your dashboard. It only takes a minute to integrate!
Available from iOS 8.0 – learn more in my book Pro Swift
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Link copied to your pasteboard.