7 comments

[ 2.5 ms ] story [ 25.2 ms ] thread
[flagged]
This is lisp. S-expressions are almost always spelled sexp and it's been like that since the 50s. This is not a real issue
I think keyword filters haven't managed to prevent widespread awareness of sex. News of sex has even reached Scunthorpe.
Haha, funny. I also wrote something similar for working with KiCad files, naming it Sexprs, also in Rust. I was worried someone had found it and posted it here.

Is there a way to modify and re-emit them at runtime? Seems neat, but the readme is lacking.

The code in the screenshot/asciinema isn't s-expr by any common conception of the term, or as a Lisp would parse it.

  (flatten '( '(a '( b)) '( c   d)))
That argument to flatten is in fact [macroexpanding manually, forgive errors]

  '((quote (a (quote (b)))) (quote c d))
which flattens to

  '(quote a quote b quote c d)
---

Parsing sexprs is quite easy, no need to use a complex parser generator. The core of parsing sexprs is you have a "read_list" function, which accumulates values until it finds a ')', and whenever you encounter a '(' character, you recurse into that same read_list function. You don't even need a lexer.

Also, this is divided in 8 crates for some reason... don't take this the wrong way, but is it the result of vibe coding?

Doesn’t seem vibe coded to me. The crates aren’t unreasonable: data structures, parser, formatter, repl, “util,” some proc macros (which have to be in a separate crate in rust), and a VM.
(comment deleted)