Immutability

[smizell]

I am interested in making the getters and setters be immutable. This means that when you set a value, the old value is not changed, but rather a new object is returned. This requires some fancy work to pass changes up and down the hierarchy and to share the tree, which shouldn't be too hard.

When it's done, it could be a really cool library for use with React, as a component could listen in on only one part of the tree using callbacks.

[fosrias]

What about performance with that overhead of duping the object and then changing?

[smizell]

No need to dupe the object I don't think. Since we are not using a data
structure here and simply JS objects for each value, we can share the whole
tree and only change the one value while saving the previous.

On Saturday, February 14, 2015, Mark W. Foster [email protected]
wrote:

What about performance with that overhead of duping the object and then
changing?

—
Reply to this email directly or view it on GitHub
#13 (comment).

[smizell]

I'm going to table this idea for now.

[smizell]

Well, I'm going to leave this open, as this may be something for future releases. I found this and it may actually be a cool fit for the internals of this if immutability is desired.

https://github.com/facebook/immutable-js