Krypt
Krypt
> A wild idea: it looks like `ForKeys`, `ForValues` and `ForPairs` accept a _callable_ object, not just a function. So, it should be possible to add a `__call` metamethod to...
Why not just ```lua Observer({state1, state2, ...}):onChange(...) ``` From what the computed example has, it would still update every time either one of the two states changes? Unless I'm not...
That... was a mountain of information 😆 I'd definitely like for the Spring and Tween objects to be rewritten, like you said it could make a for a reduced motion...
This can be closed due to the above being merged!
Is there going to be any difference between this and `peek()`? Provided that we're adding that.
Doesn't seem like a bad solution, we could do a benchmark with JSONEncode
Oh yeah forgot about that edge case, bit annoying unfortunately.
I wouldn't create a PR just yet only because this issue is marked as `status: needs design`. PR's are generally meant for approved features (a mistake I made twice so...
This might be redundant due to #216 being written.
> This implementation also breaks when the state result is nil, as was given as a usecase in the original issue. Didn't realise this! Will update! > "avoiding unnecessary memory...