Memoization assumes a function's observable effect is fully captured by its return value (plus its declared target states). But sometimes there're dependencies or effects that live outside that:
- Live components: which has live updates over time
- Source read: data read through most sources provided by CocoIndex are supposed to change over time
We want to build an API to invalidate memoization for the entire call stack. The API should be called by the operations above, and will also be used for similar cases in the future.
Memoization assumes a function's observable effect is fully captured by its return value (plus its declared target states). But sometimes there're dependencies or effects that live outside that:
We want to build an API to invalidate memoization for the entire call stack. The API should be called by the operations above, and will also be used for similar cases in the future.