Daniel P H Fox

Thought I'd drop in to give a quick update on this. It turns out there's a bit of ambiguity over what counts as 'deeply equal' - I was discussing this...

That's also what I'm considering right now - we *would* be breaking the mental model of state objects as variables a bit, but perhaps that's a net positive.

That's certainly a possibility, but it's worth noting there that your solution doesn't work if the table contains a `set` key. It would be better to externalise the behaviour of...

For sure - I think this is a much preferable solution where its applicable.

This would enhance the current suboptimal semantics around yielding code right now - instead of having to resort to using a Compat to listen and send off yielding changes, it'd...

So I've been considering this for a while, and with the advent of explicit dynamic dependencies (see #111) it should now be possible to extend the idea of a Computed...

After further discussion in the OSS discord, leaning towards rolling the former solution into Computed using a symbol: ```Lua local number = Value(5) local plusOne = Computed(function(use) task.wait(5) -- this...

I should probably drop these thoughts here from the Discord: > yeah I'm always searching for the most theoretically fitting answer, and the first solution lines up more with how...

One point of contention that has come up here is about how the resolution status of an `Eventual` or `Computed` is to be represented. There are a few philosophies here:...

One interesting line of thinking here - should an `Eventual` be able to control it's value during yielding? Perhaps, instead of providing a `Pending` symbol/monad/equivalent, it returns one value for...