Why do we need to mark some methods as mutating?
Updated for Xcode 15
It’s possible to modify the properties of a struct, but only if that struct is created as a variable. Of course, inside your struct there’s no way of telling whether you’ll be working with a variable struct or a constant struct, so Swift has a simple solution: any time a struct’s method tries to change any properties, you must mark it as mutating.
You don’t need to do anything else other than mark the method as mutating, but doing that gives Swift enough information to stop that method from being used with constant struct instances.
There are two important details you’ll find useful:
- Marking methods as
mutatingwill stop the method from being called on constant structs, even if the method itself doesn’t actually change any properties. If you say it changes stuff, Swift believes you! - A method that is not marked as mutating cannot call a mutating function – you must mark them both as mutating.
SPONSORED Join a FREE crash course for mid/senior iOS devs who want to achieve an expert level of technical and practical skills – it’s the fast track to being a complete senior developer! Hurry up because it'll be available only until April 28th.
Sponsor Hacking with Swift and reach the world's largest Swift community!
