It makes no sense to cache large values that are fast to compute. Likewise, once we need to clear memoized values to free space, we need to decide which values to remove.
Desired solution
When memoizing, also track
last access,
time to compute value,
time to perform lookup in memoization table (equality check can also be expensive),
Is your feature request related to a problem?
It makes no sense to cache large values that are fast to compute. Likewise, once we need to clear memoized values to free space, we need to decide which values to remove.
Desired solution
When memoizing, also track
Then evaluate different strategies for
Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
No response