kind of. For example, in Java, build tools will normally cache the hash of the source file that generated a class file. That class file is a cached version of

kind of. For example, in Java, build tools will normally cache the hash of the source file that generated a class file. That class file is a cached version of the source, basically. IF you could keep both the class file and the hashes of the source around, you could avoid ever re-compiling the source unless you've changed it. This is just incremental compilation, in essence. However, you'll need quite a lot of tooling around this simple idea: where to store the class files and the hashes, should you commit it into source control, how to distribute the cache, can this be made multi-platform so it works on all developers' machines? All solvable, but Unison already does all that, and more, with its single tool, the `ucm`.