3 ms·
Feels like we're 5-10 years away from "Lisp as an alternative to Go".
by neolog 6y ago
Feels like we're 5-10 years away from "Lisp as an alternative to Go".
- szopa 6y agoI'm waiting for "Lisp as an alternative to Rust." :)
- modderation 6y agoWhy not get the best (?) of both worlds with the macro-lisp crate: https://github.com/JunSuzukiJapan/macro-lisp https://github.com/JunSuzukiJapan/macro-lisp A small snippet from the project's examples shows minimal boilerplate between Rust and a native-looking Lisp experience: lisp!(defun factorial ((n i32)) i32 (if (<= n 1) 1 (* n (factorial (- n 1)))));
- bitwize 6y agoOrange crab bad!
- erik_seaberg 6y agoThere are several abandoned Clojure/Go projects out there, and I can’t be the only one thinking about how Common Lisp displaced arrays and multiple values and exported package symbols resemble core Go features. The catch is using type declarations to drive codegen, when so many types can be passed by value or reference. And single dispatch for methods, when CL tends to choose CLOS or nothing. But my north star is to write REMOVE-IF-NOT and get the dozen lines of noise it takes to bubble errors and fill a new slice.
- closeparen 6y agoAs a large, mature Go shop we have several “macros” that are now quite load-bearing. They’re based on Bazel rules and text/template. Get support for these workflows (which are increasingly common) into the upstream toolchain, combine with the “AST” package and pretty printer, and Go is well on its way to being a Lisp.