Jared Sinclair

Be Careful When you Initialize a StateObject Property Wrapper — https://jaredsinclair.com/2024/03/14/state-object-autoclosure.html

There’s an easy pitfall to fall into, and it can totally undermine the reason you're using StateObject in the first place.

Jared Sinclair | Be Careful When You Initialize a State Object

Mar 14, 2024 at 3:53pmIvory for Mac
Show threadChris Wu 🪐Mar 14, 2024
@jaredsinclair I am so bookmarking this to read later.
Show threadAdam OverholtzerMar 14, 2024
@jaredsinclair Good article, but I tried your suggestion and the compiler doesn't like it…?
Show threadJared SinclairMar 14, 2024
@adam Thanks. I was typing the code samples straight into Markdown from memory.
Show threadJared SinclairMar 14, 2024
@adam I'll push up some fixes in a bit.
Show threadJared SinclairMar 14, 2024
@adam This is exactly why an autoclosure here is so misleading.
Show threadOle BegemannMar 17, 2024

@jaredsinclair Great post! Small clarification on explicit view identity: the .id() modifier acts in *addition* to the structural identity defined by the view’s position in the view hierarchy. So .id() can never make two non-identical views identical, only the other way around. These two views have different identity despite having the same .id():

if flag {
MyView().id("one")
} else {
MyView().id("one")
}

Show threadpaxosMar 18, 2024
@jaredsinclair any thoughts re: Apples recommendation to use State (instead of StateObject) in combination with Observation? Because in my testing this is not working at all.
Show threadChristian TietzeMar 18, 2024
@jaredsinclair this is an excellent summary! I put off writing about this for over a year, and now I'm happy to scrap the draft and just link to yours :)
Show threadJared SinclairMar 18, 2024
@ctietze lol mine took over a year as well
Show threadChristian TietzeMar 18, 2024
@jaredsinclair ha, maybe it's part of the complexity of this ... uh.. """interesting tool""" :)