funwolf7

> This is only necessary as an alternative to #144. If that's added, it implicitly avoids the intermediate calculation if not required. It also easily solves the second comment regarding...

After thinking about this some more, I think that I prefer the batching idea. It falls more in line with what I would personally use it for; I mainly just...

```lua batchSet { { aValue, 2 }, { bValue, "foo" }, } ``` This seems impossible to typecheck as well. Using an array for combining the Value and property into...

Thinking about my past situations where I thought I needed batch setting, I probably could have used a Value that stores a table of information and Computeds to get individual...

> When we say something like `WithChild "Thing"`, what do we mean? Is it the "Thing" at the current time, or whatever "Thing" will be at any point in time?...

I realized that a bit after posting it. The manual cloning can (in fact it must) be skipped the first time, but it still must be done whenever the child...

These are valid points. This was mainly in response to the quote: > or whatever "Thing" will be at any point in time? which sounds a to me like changing...

I decided to attempt to code this up and finished a prototype, but when going to test it, I ran into a problem. Consider the case where someone wants to...

An alternative to the above idea of returning nil is to allow returning state objects, which will then automatically change the table (without running the processor function again) when they...

I experimented with allowing the processor to return StateObjects and I really like it. It allows for more complicated processors that run less often. Consider the following example, where `extremelyExpensiveFunction`...