KeenanKeenan

>Programming has developed an unfortunate tone.

> We kill processes, abort transactions, throw exceptions, break out of loops, and execute instructions.

Can't wait to see the fork of this project that doubles down on hostile language /s

Typed racket too, might I add. I just imagine static typing around stable core APIs would help users understand how eglot and vertico compare to prior art. The way I learned how the completion stack works was to ask claude to show me what the elisp entrypoints would look like if implemented in typescript. It's not because I'm unfamiliar with lisp, I'm not, it's just easier to reason with the world in terms of data structures and their contracts.

If macros can implement arbitrary language features then how come elisp has never built a type system?

I love cucumber but I never follow the pattern to (1) write the feature file, (2) generate partially implemented tests with said file, (3) finish implementing the tests + subject under test.

It's better to (1) write the test, (2) then later once all that's done, extract documentation in a human-friendly format.