{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"SwiftUI’s @State Is Now a Macro - What It Means for You","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/8cfc6592\"></iframe>","width":"100%","height":180,"duration":219,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/swiftuis-state-is-now-a-macro-what-it-means-for-you.\nSwiftUI’s @State is now exposed as a macro. Learn what changed, how lazy initialization works, and how to use @State with @Observable models.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #swift, #swiftui, #ios-app-development, #ios-development, #swift-programming, #apple, #swift-changes, #hackernoon-top-story,  and more.\nThis story was written by: @element. Learn more about this writer by checking @element's about page,\n            and for more stories, please visit hackernoon.com.\nTL;DR: SwiftUI’s `@State` is now exposed as a macro, but everyday usage stays almost the same. The biggest practical change is lazy initialization: class instances stored in `@State`, such as `@Observable` view models, are created once for the lifetime of the view’s state storage instead of being re-created whenever the view struct is rebuilt.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}