-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about "No weak-mappable object" #3
Comments
Yes, you are correct. However, sooner or later, you might end with I know - some string calculations, as well as Fibonacci numbers, could be very CPU intense, but you will have use other memoization technology, with explicits cache, to handle them, not There is also a case, when you are returning an object from such "complex" function - |
Hi,
Thanks for your library and documentation. It's very nice to find a library which explains what and how it solves some cache performance issues.
I've fully understood how it works now. All my arguments are objects and there is no non weak mappable objects as arguments when I call my selector.
I still have an issue concerning a selector which compute a result from multiple sub selectors which return all non weak mappable object (all booleans), and have an error.
In your documentation, you mention to use an external cache object but I guess, it should not be a global object that will never be unreferenced as it cache will never be cleared.
If I understand well, it will be better to have a weak mappable object, which also have his lifecycle and will be garbage collected to have my values being cached while this object still exist.
Am I right?
The text was updated successfully, but these errors were encountered: