3 ms·
This is nice, I didn't know about named-let being usable for tail recursion. I have always liked the idea of a Emacs Lisp back end for Purescript and having ta
by throwaway81523 4y ago
This is nice, I didn't know about named-let being usable for tail recursion. I have always liked the idea of a Emacs Lisp back end for Purescript and having tail recursion makes it easier. Purescript is a typed functional language that is sort of a modernized Haskell with strict evaluation, originally written to give a typed language that compiles to Javascript, but now it has more backends while Typescript seems to have occupied the "typed JS" niche that Purescript had hoped to fill. (www.purescript.org for more info). Anyway, it would be cool to generate Emacs Lisp code from Purescript and get rid of a lot of wrong-type-arguments errors at runtime.
- medo-bear 4y ago> and get rid of a lot of wrong-type-arguments errors at runtime like which ones?
- throwaway81523 4y agoIf you have used Emacs for any length of time you will have run into them now and then. The usual sort is when something is expected to be a value but instead it is nil, the equivalent of a null pointer exception. It's hard to give examples because if there was a reproducible one that happened often enough to remember, it would go through the bug fix process. Instead it just happens enough to be annoying. I guess gnus.el is a common subsystem where it happens a lot, say if a remote server is down.
- medo-bear 4y agofor past 5 years, 90% of things i do is done in emacs. type errors have never been an annoyance to me and i do not recall comming across them at all. thats why i asked. pitty you can't give me an example