One pattern that I have frequently used in EMACS elisp is that redefining a top-level value overwrites that value rather than shadowing it. Basically hot reloading. This doesn't work in a dependently typed context as the type of subsequent definitions can depend on values of earlier definitions.
def t := string
def x: t := "asdf"
redef t := int
redefining t here would cause x to fail to type check. So the only options are to either shadow the variable t, or have redefinitions type-check all terms whose types depend on the value being redefined.
Excluding the type-level debugging they mention, I think a lean style language-server is a better approach. Otherwise you are basically using an append-only ed to edit your environment rather than a vi.
fithisux · 33m ago
Impressive.
reikonomusha · 1h ago
Related context: The 2025 European Lisp Symposium [1] was just wrapped a few hours ago in Zurich. There was content on:
- Static typing a la Haskell with Coalton in Common Lisp
- Dependent typing with Deputy in Clojure (this post)
- The Common Lisp compiler SBCL ported to the Nintendo Switch
Any URL for this that we can open in a browser (as opposed to the dreaded "Content-Disposition: attachment")?
Jtsummers · 1h ago
https://zenodo.org/records/15424968 - This at least takes you to a webpage where you can view the paper. If you select to download it, it still downloads of course instead of just opening in the browser.
dang · 1h ago
Thanks! I've switched to that above, and put the downloadable link in the top text.
The only hint is this repo[0] referenced in the paper.
[0]: https://gitlab.com/fredokun/deputy
One pattern that I have frequently used in EMACS elisp is that redefining a top-level value overwrites that value rather than shadowing it. Basically hot reloading. This doesn't work in a dependently typed context as the type of subsequent definitions can depend on values of earlier definitions.
redefining t here would cause x to fail to type check. So the only options are to either shadow the variable t, or have redefinitions type-check all terms whose types depend on the value being redefined.Excluding the type-level debugging they mention, I think a lean style language-server is a better approach. Otherwise you are basically using an append-only ed to edit your environment rather than a vi.
- Static typing a la Haskell with Coalton in Common Lisp
- Dependent typing with Deputy in Clojure (this post)
- The Common Lisp compiler SBCL ported to the Nintendo Switch
- Common Lisp and AI/deep learning
- A special retrospective on Modula and Oberon
- Many lightning talks.
[1] https://european-lisp-symposium.org/2025/index.html
No comments yet