Interesting, I had not considered that. Makes sense.
But ... doesn't it seem like the compiler or runtime would at least give me a warning that using @State with a class has the problem you described? Or is there a case where @State with a class is the right thing to do?
Robert
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags: