Unison, and why the codebase of the future is a purely functional...
summary
Unison identifies every definition by a content-addressed hash (real system uses 512-bit SHA-3), stores a serialized AST per hash plus name metadata, and keeps a persistent shared test and compile cache keyed by hashes. That lets the codebase be an append-only functional data structure: instant, always-accurate renames, cached deterministic test results so tests rarely rerun, and controlled refactorings via patch mappings from old-hash to new-hash. Live demo shows the editor, scratch files, watches and updates working end-to-end.
AI-written summary · about
chapters (6)
- 0:00Introduction to Unison
- 1:53Code identified by hash
- 5:07Benefits of hash-based code
- 11:36Live demo of Unison
- 20:01Refactoring without breaking
- 30:42How to try Unison
related talks
19mUnison: A Friendly Programming Language from the Future Part 1
27mUnison: A Friendly Programming Language from the Future Part 2
41mIntroduction to the Unison programming language
31mBuilding a Sustainable CodeBase with FP
42mFunctional Programming in 40 Minutes
34mImmutability: Putting The Dream Machine To Work
01h 44mFunctional Programming: Technical Reasons to Adapt
01h 04mFunctional C++ For Fun And Profit