Skip to content
#

memoization

Here are 196 public repositories matching this topic...

uazure
uazure commented Jul 18, 2019

I tried to use this memoizer for fuction with 5 arguments, and I implemented the custom cache with .get() .set() and .has() methods

We have 100% test coverage rule for our code. And after running tests I see that .has() method is never called. I checked the source code for fast-memoize and I see no usage of .has() method at all.

So, either documentation should be updated to not mention the .

madpin
madpin commented Nov 1, 2019

Well, my use case is:
I have a function that queries the database, the input is the database alias and the query.
It's working great, but I just saw that the cache size will grow indefinitely, right?
My idea was to keep track of the stale date, and check for all elements of the object if any was already "staled", and delete it.
Just to keep the filesize at a minimum.

I never worked with Cla

flavius
flavius commented Apr 14, 2019

I just skimmed through the docs, so bear with me:

I have two functions, one is cached, and another one might invalidate the cache or some key in it. There's no example of how to get ahold of the cache in the second function, in order to be able to call methods like cache_remove or cache_clear.

The second function is not cached, it just invalidates the cache, and there can be an infinite

Improve this page

Add a description, image, and links to the memoization topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the memoization topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.