Meta Messaging Interoperability (developers.facebook.com)
1 points by niemandhier 21m ago 1 comments
Liora Journal – Digital Journaling Assistant (liorajournal.com)
2 points by newnix 1h ago 0 comments
The AGI economy is coming faster than you think (freethink.com)
8 points by levlaz 2h ago 1 comments
It's time for California home prices to fall (ocregister.com)
2 points by harambae 2h ago 1 comments
Of Course ML Has Monads (2011) (existentialtype.wordpress.com)
2 points by Bogdanp 2h ago 1 comments
The Lisp in the Cellar: Dependent types that live upstairs [pdf]
88 todsacerdoti 19 5/20/2025, 1:38:07 PM zenodo.org ↗
Downloadable: https://zenodo.org/records/15424968/files/deputy-els.pdf
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.
And it is called that for a reason, it is not very dynamic :) and probably too static to the taste of many Lisp and all Smalltalk fans.
I used this to write the front end for an ATM machine.
- 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
Lisp was the de facto language of artificial intelligence in the U.S. for many years. Apparently Prolog was popular in Europe (according to Norvig's PAIP)
Peter Norvig, 1992
Paradigms of AI Programming: Case Studies in Common Lisp
https://g.co/kgs/hck8wsE
https://en.m.wikipedia.org/wiki/Peter_Norvig
it's no coincidence Google is actively maintaining sbcl, either.