What's in a language?
summary
Claim: modules in Reason/OCaml push meta concerns (file layout, mixins, docs, API surfaces) into the language so less ad‑hoc codegen is needed. Evidence: BuckleScript compiles includes away with no runtime cost; build system implicitly wraps files as first‑class modules and nested modules act like folders; module signatures are inferred or autogenerated and module types map to .mli interface files that produce checked, publishable docs and enforce public API boundaries. Practical result: React bindings and libraries behave as typed, zero‑cost abstractions.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:48The primitive language
- 3:34Reason
- 4:04Ladder
- 5:06Filesfolders
- 5:38Modules
- 8:42What do we push down
- 10:50File is a module
- 13:57Modules types
- 15:47Documentation
- 20:32Encapsulation
- 27:57Conclusion
- 30:27Questions
