comemo VS bkt

I wonder how this compares to comemo [1] [2], they're both memoization frameworks with "tricks" to limit invalidation.

The trick in comemo's blog post is to make the dependencies fine-grained, by tracking and only comparing what parts of them are actually used; while the trick here is to have functions depend on other outputs instead of the root input, so changes don't propagate all the way.

[1] https://laurmaedje.github.io/posts/comemo/

[2] https://github.com/typst/comemo

Hi, author of bkt here. I use fzf all the time and combine it with bkt to make --preview faster. I hope you find this pattern useful!

Alternatively, check out bkt (also mine), which is like bash-cache but for subprocesses instead of shell functions.

Instead, using bkt ensures each request is only sent once and all subsequent calls return locally cached results:

Enjoy! If you find it useful please let me know how you're using it!

Honestly, any reasonably complex bash script uses (or should be using!) arrays, so just poke around and you'll probably see them. Here's a fairly straightforward script of mine with several arrays: https://github.com/dimo414/bkt/blob/master/benchmark.sh

Glad to hear it! I hope you find it helpful :) If you have a few minutes please share how you're using bkt, it'll help me and others!