May 9, 2026
Paren-theses and fury
Rust but Lisp
Rust gets the Lisp treatment, and the comments are asking: "...but why?"
TLDR: rlisp lets people write Rust in a Lisp-style parenthesis format, then turns it into normal Rust code with no extra engine attached. The big reaction was split between amused confusion, style-police outrage, and a smaller crowd insisting the whole weird idea is exactly the point.
A new project called rlisp promises something delightfully chaotic: Rust, but written with a wall of parentheses. It takes a Lisp-style look and turns it directly into regular Rust code, which then gets checked and compiled as usual. In plain English, the creator is saying: you can keep Rust’s strict rules and speed, but type it like an old-school Lisp wizard. And yes, that instantly turned the comment section into a tiny civil war.
The loudest reaction was pure disbelief. One deadpan commenter summed up the mood with a brutally simple “And for why?” Others said this isn’t really a fresh new language at all, just Rust wearing a Lisp costume, and not even a very convincing one if you actually like Lisp. That sparked the central drama: is this a clever bridge between two beloved coding styles, or a cursed syntax experiment nobody asked for?
But defenders jumped in fast. Their pitch: that’s the whole point. This isn’t trying to invent new behavior, only a new way to write it. Fans argued that people who love Rust’s strict “you must do things correctly” style might enjoy seeing those same rules in a parenthesis-heavy form. Meanwhile, the jokes were flying. One commenter practically launched a one-person campaign against the phrase “no runtime, no GC, just…”, calling it the latest flavor of AI-generated doc-speak. And of course, someone immediately went hunting for missing edge cases like lifetimes and the infamous “turbofish,” because no Rust debate is complete without somebody demanding the hardest syntax first.
Key Points
- •rlisp is described as a Lisp-style s-expression frontend that preserves Rust semantics and transpiles to Rust source code.
- •The article states that rlisp adds no runtime or garbage collector, with `rustc` handling checking and optimization on generated code.
- •It provides installation instructions and CLI commands for compiling, building, and running `.lisp` source files.
- •A syntax map shows rlisp equivalents for many Rust constructs, including functions, structs, enums, traits, matches, loops, macros, closures, and visibility modifiers.
- •The macro system is presented as compile-time transformation of s-expressions using `quasiquote`, `unquote`, and `unquote-splicing`, with examples such as `when` and `double`.