Daniel P H Fox

There wouldn't be a need to clone the child instance manually; `:Clone()` is recursive already.

I don't think we're on the same page. I've been under the assumption that `New(instance)` == `Hydrate(instance:Clone())` - at least, that was the original design intention. I can perhaps see...

Yes, timers tick up forever. They are not floored, they use real numbers of seconds. This has no memory implications.

I will not pursue this for now.

From my. conversations with others, there seems to be little appetite for this. Closing in favour of #291.

Another idea I like, though it doesn't address all the motivating problems, is the ability for value objects to give away write control over their value, turning the object itself...

> I think it makes more sense to do that as `local foo, access = ReadOnly()`. > One-time operations on a State don't fit well in the reactive graph, and...

Merging with #87

Merging with #206

@Hexcede you make some valuable points about preserving existing use cases here. We should definitely look into some way of ensuring both immutable and mutable use cases are supported pretty...