Here I’m seeing SwiftUI (framework) decision to trigger onChange in case of let that feels unexpected from the Swift (language) perspective. This behavior could be unreliable or unintended. I'd like a definitive answer on whether this is supported behavior or simply SwiftUI being unable to express intent of supporting only mutable state in Swift. I'd like to be able to use documentation to know if this code is safe to use or if it may behave differently in future SwiftUI versions.
dratkevich
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for