@simonbs my LELIT p62t is currently in maintenance (aka dismembered next to my desk) and I’m starting to fear that if you keep posting about this machine I’ll end up buying it 🙈 !
@dimillian, I love the idea of the new indentation marker but I feel like it’s a bit too much as soon as you get to 2 or more levels.
How do you feel about these ? I’d be happy to draft a PR about it !
Sometimes I see something that makes me go: “How can one person achieve so much by themselves? They must be so smart!” Then I learn they’re just a jerk nobody will work with.
And they are smart, of course. But I’m left wondering what would be possible if they weren’t a jerk.
Can anyone think of a design pattern that makes it easy and safe to keep the state of child objects in sync with their parent? I.e. when a property is updated on a parent object, the new value should be forwarded to its children.
The naive approach is to override didSet on the parent's property and forward the new value to the children but it’s easy to forget to update the implementation of didSet when new children are introduced.
@simonbs I may have missed something in your different solutions but wouldn’t a Reference class that stores only one property at a time be a solution ?