A memoization library which only remembers the latest invocation
Stateless weak memoization replacement for reselect and memoize-one
A memoization algorithm that only caches the result of the latest set of arguments, where argument equality is determined via a provided equality function.
memoize the last result, in async way
memoize-one for react
A memoize-one function that analyses the function output and retains previous object references wherever data hasn't changed
fork of fast-memoize and support esm
powerful memorization lib, which inspired by memoize-one, proxy-memoize
A `memoize-one` wrapper that resolves the latest invocation asynchronously
A memoization function that uses a WeakMap
Fastest memoization lib that supports N arguments
A blazing fast memoization library that is tiny but feature-rich.
Memoize functions - An optimization used to speed up consecutive function calls by caching the result of calls with identical input
Memoize decorator for Typescript
Memoize promise-returning & async functions
The lodash method `_.memoize` exported as a module.
Intuitive magical memoization library with Proxy and WeakMap
A memoization library which only remembers the latest invocation. Built with TypeScript and includes decorators.
Fast memoization decorator and other helpers with 1st class support for Promises.
Memoize/cache function results
Faster than fast, smaller than micro ... a nano speed and nano size memoizer.
A general purpose key resolver for memoize
Ultra fast, zero config memoization of functions
Memoization utilities for cacheable
One line method memoization for ruby classes.
VERY SIMPLISTIC memoization for functions (one memoized value per function; no regard for arguments). Uses UnboundMethods instead of method aliasing, so you don't see extra method names when you inspect your object.
Like Memoize, but designed for mutable and parametizable objects Use when: 1. You have one expensive method (\compute) which set many internal variables. So, is preferable lazy evaluation of these dependent variables. 2. The expensive operation depends on one or more parameters 3. Changes on one or more parameters affect all dependent variables 4. You may want to hide the call of 'compute' operation 5. The user could want test several different parameters values