ObjectState copy on write, and emit a copy of its internal state object. about objectstate HOT 4 CLOSED

I don't know how I feel about this-- it strikes me as non-idiomatic, and as though objectstate is concerning itself with how it is used, rather than doing its job well. I'd prefer we leave it to clients to copy or not as they see fit. Then they can choose the solution that's correct for them.

We are letting them shoot themselves in the foot, but so is JavaScript.

from objectstate.

the ability to set things outside of streaming to them (via .set()) is a very important feature that single-handedly puts the object-handling ball back into OS's court.

OS managing the copying seems to be the only way to prevent leakiness.

from objectstate.

For #12, We also need to copy whenever we check to see if we should emit or not, which means we accrue the performance costs of the copy anyway.

Additionally, if we DONT copy, client modules could mutate state without the objectstate ever hearing about it, which contravenes its purpose of encapsulating global state and emitting whenever it changes.

from objectstate.

fixed in 180f07f

from objectstate.