> > > > I don’t understand why we need the `mutating` keyword in the first place. > Is it for readability? Right now the compiler knows when a function mutates > a property and forces us to write `mutating`. Couldn’t it just fail > compiling when try to call a mutation function but we’re not allowed? > > I strongly disagree with this sentiment. I agree that the compiler can figure it out without us in many cases but I appreciate knowing *explicitly* which parts of an API will mutate a value. It is helpful for both the vendor and consumer of the API to require that keyword.
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
