Erm, not really. Compiler cache saves compiled versions of files. When building a large project it notices things that have been built before and looks up the c

Erm, not really. Compiler cache saves compiled versions of files. When building a large project it notices things that have been built before and looks up the compiled code from a central cache. If you have to do a "make clean" (e.g. some scripts for making Debian packages start this way) you still get fast re-builds. The linked article is about run-time memoization: rather than caching the compiled version of a function's code, you cache just the output of the function for particular inputs.