Remove fast-memoize from docs

[mfbx9da4]

I would strongly recommend against using fast-memoize in these docs. It will jsonify the incoming argument parameters. The user is likely to be memoizing against large state objects. The cost of stringifying these large objects could easily outweigh the performance benefits of memoization.

fast-memoize is well benchmarked for use cases when you are memoizing a function which takes small integers as arguments. fast-memoize benchmarking also does not incorporate key deletion or any polymorphic pressure exerted on the engine. For easy peasy, most of the time in my experience, you are memoizing large objects as keys in the memoized cache. Memoizerific and other memoization libraries are able to cache objects effectively because the javascript engine stores a random ID on every object and ES6 Map is able to use that ID. Therefore object lookup in a Map will amount to an integer comparison whereas with fast-memoize this comparison will amount to serializing the entire object and then comparing long strings.

[codecov]

Codecov Report

Merging #663 (f174fe4) into master (5c4c0e8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #663   +/-   ##
=======================================
  Coverage   94.97%   94.97%           
=======================================
  Files          18       18           
  Lines         696      696           
  Branches      139      139           
=======================================
  Hits          661      661           
  Misses         30       30           
  Partials        5        5           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5c4c0e8...f174fe4. Read the comment docs.

[ctrlplusb]

Excellent insight. 🙏