ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
memoize cache expiration policy Goal: determine how to enforce a time‑to‑live (TTL) for entries returned by clojure.core/memoize . Constraints: memoize stores results in a mutable atom and never expires entries; no built‑in TTL or eviction strategy. Manual cache clearing is required, but the API does not expose a convenient mechanism for per‑key TTL or autom
Goal: guarantee that a memoized subroutine returns up‑to‑date data when the underlying external resource (e.g., a file or database) changes, including after a process fork where the child should see its own environment. Constraints: the Memoize module stores results keyed only by argument values and never expires entries automatically; after a fork the child
lodash _.memoize unbounded cache retention The goal is to use lodash _.memoize in a low-traffic Node service without allowing the memoization cache to grow without bound from unique or high-cardinality arguments. In lodash 4.x, _.memoize stores results in a .cache Map keyed by the first argument or a custom resolver and retains entries until the process exit
Confirm whether Lodash _.memoize incorporates every function argument into the default cache key, or only the first argument, when caching results in Lodash 4.x. The default resolver appears to stringify only the first argument. If true, calls such as fn(1, 2) and fn(1, 3) could return the same cached value because the trailing argument never participates in
clojure
perl
lodash
nodejs