Second, we address a major usability flaw in Typed Clojure: users must manually write annotations. To
remedy this, I will present a tool that automatically generates Typed Clojure annotations based on observed
program behavior, including a formal model of the tool, consisting of its runtime instrumentation phase that
collects samples from a running program, and type reconstruction phase that creates useful annotations from these
samples.
I’ve wondered about this approach for a while. If it works for Clojure it might also be a boon for Typescript/Flow, or for getting more type hints into Python (which, IMO, is less useful given the official stance against type checking)
I’ve wondered about this approach for a while. If it works for Clojure it might also be a boon for Typescript/Flow, or for getting more type hints into Python (which, IMO, is less useful given the official stance against type checking)