🎉 Finally, finally found use for defer. You can force a didSet to fire from within a class init like so 🎉
15
119
323
Conversation
That’s sneaky! Almost feels like a bug!
1
3
nope. init does not trigger didSet blocks. defer means your code will be executed after init has finished, which is okay
2
2
It is executed after the body of init, but it is still part of init... this really feels like a bug. //cc
2
5
1
3
Hrm. I'd say it's a bug—comes from implementing defer on top of closures. If you want didSet behavior in init, call a helper method.
2
1
5
Uh oh, I've been relying on this for a while. I'm glad we wrote a test at KA to ensure this behaviour didn't disappear 😅
1
4
Haha oh man I expected this to go away at some point. Good! I feel this was a wart on the language semantics.
1
3
I discussed this with once, wanted to opt properties in under certain constraints. IIRC prop behaviors was the great hope
1
Sure, yeah, I’d be interested in some intentional way to explicitly indicate “yo please treat this like a post-init setter”
well, it's official. I once again have no use for defer in my life 😂
1
8
I love defer. Example:
defer { x += 1 }
return x
2
Show replies