#lisp — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lisp, aggregated by home.social.
-
🚀 Oh joy, another #language mashup! #Coalton combines all your favorite parts of #Haskell, #OCaml, and #Lisp to create... well, something nobody asked for. 😂 Just what we needed: Common Lisp with a personality crisis. 🤔
https://coalton-lang.github.io/ #mashup #programming #humor #HackerNews #ngated -
🚀 Oh joy, another #language mashup! #Coalton combines all your favorite parts of #Haskell, #OCaml, and #Lisp to create... well, something nobody asked for. 😂 Just what we needed: Common Lisp with a personality crisis. 🤔
https://coalton-lang.github.io/ #mashup #programming #humor #HackerNews #ngated -
🚀 Oh joy, another #language mashup! #Coalton combines all your favorite parts of #Haskell, #OCaml, and #Lisp to create... well, something nobody asked for. 😂 Just what we needed: Common Lisp with a personality crisis. 🤔
https://coalton-lang.github.io/ #mashup #programming #humor #HackerNews #ngated -
🚀 Oh joy, another #language mashup! #Coalton combines all your favorite parts of #Haskell, #OCaml, and #Lisp to create... well, something nobody asked for. 😂 Just what we needed: Common Lisp with a personality crisis. 🤔
https://coalton-lang.github.io/ #mashup #programming #humor #HackerNews #ngated -
🚀 Oh joy, another #language mashup! #Coalton combines all your favorite parts of #Haskell, #OCaml, and #Lisp to create... well, something nobody asked for. 😂 Just what we needed: Common Lisp with a personality crisis. 🤔
https://coalton-lang.github.io/ #mashup #programming #humor #HackerNews #ngated -
Coalton is an efficient, statically typed Lisp with ideas from Haskell and OCaml
https://coalton-lang.github.io/
#HackerNews #Coalton #Lisp #Haskell #OCaml #programming #language #development
-
Coalton is an efficient, statically typed Lisp with ideas from Haskell and OCaml
https://coalton-lang.github.io/
#HackerNews #Coalton #Lisp #Haskell #OCaml #programming #language #development
-
Coalton is an efficient, statically typed Lisp with ideas from Haskell and OCaml
https://coalton-lang.github.io/
#HackerNews #Coalton #Lisp #Haskell #OCaml #programming #language #development
-
Coalton is an efficient, statically typed Lisp with ideas from Haskell and OCaml
https://coalton-lang.github.io/
#HackerNews #Coalton #Lisp #Haskell #OCaml #programming #language #development
-
Coalton is an efficient, statically typed Lisp with ideas from Haskell and OCaml
https://coalton-lang.github.io/
#HackerNews #Coalton #Lisp #Haskell #OCaml #programming #language #development
-
Clojure on Fennel part three: parsing https://lobste.rs/s/qtno6s #clojure #lisp
https://andreyor.st/posts/2026-04-27-clojure-on-fennel-part-three-parsing/ -
@withinity the #Lisp hashtag has been quite busy with the #LispGames #GameJam lately, but for broader gamedev stuff just look at #GameDev.
-
@withinity the #Lisp hashtag has been quite busy with the #LispGames #GameJam lately, but for broader gamedev stuff just look at #GameDev.
-
I wrote a blog post about slot access in Common Lisp:
https://turtleware.eu/posts/A-brief-note-about-slot-access-cost-in-Common-Lisp.html
Enjoy!
-
I wrote a blog post about slot access in Common Lisp:
https://turtleware.eu/posts/A-brief-note-about-slot-access-cost-in-Common-Lisp.html
Enjoy!
-
CLRHack: unwind-protect and catch-throw
http://funcall.blogspot.com/2026/05/clrhack-unwind-protect-and-catch-throw.html
-
RE: https://fosstodon.org/@tarsius/116643132796222151
In 1990 Dr. Peter Lee's 15-212 course at #CarnegieMellon introduced me to Scheme. It's also when I first came to comprehend the power of #Emacs and #EmacsLisp.
In the first hour, Professor Lee demonstrated elegantly that everything is a list: data are lists and programs are lists. Every list returns a value, and functions are just lists that do calculations! Functions can return lists, of course, and so you can write functions that return functions!
I ran to the lab to hack Lisp: it wasn't in your pocket, it was in a room worth more than your parents' house. Nothing had ever seemed more natural: write, evaluate, repeat. Hack a nugget, nest lists, add parentheses, hack bigger things. But the magic thing where you write code that returns code remained a mystery: we did lots of cool stuff in that course, but we never got to macros.
Until 2026.
The surprise? The surprise is that as each decade passes, I grow to cherish lifelong learning as more and more precious.
-
RE: https://fosstodon.org/@tarsius/116643132796222151
In 1990 Dr. Peter Lee's 15-212 course at #CarnegieMellon introduced me to Scheme. It's also when I first came to comprehend the power of #Emacs and #EmacsLisp.
In the first hour, Professor Lee demonstrated elegantly that everything is a list: data are lists and programs are lists. Every list returns a value, and functions are just lists that do calculations! Functions can return lists, of course, and so you can write functions that return functions!
I ran to the lab to hack Lisp: it wasn't in your pocket, it was in a room worth more than your parents' house. Nothing had ever seemed more natural: write, evaluate, repeat. Hack a nugget, nest lists, add parentheses, hack bigger things. But the magic thing where you write code that returns code remained a mystery: we did lots of cool stuff in that course, but we never got to macros.
Until 2026.
The surprise? The surprise is that as each decade passes, I grow to cherish lifelong learning as more and more precious.
-
RE: https://fosstodon.org/@tarsius/116643132796222151
In 1990 Dr. Peter Lee's 15-212 course at #CarnegieMellon introduced me to Scheme. It's also when I first came to comprehend the power of #Emacs and #EmacsLisp.
In the first hour, Professor Lee demonstrated elegantly that everything is a list: data are lists and programs are lists. Every list returns a value, and functions are just lists that do calculations! Functions can return lists, of course, and so you can write functions that return functions!
I ran to the lab to hack Lisp: it wasn't in your pocket, it was in a room worth more than your parents' house. Nothing had ever seemed more natural: write, evaluate, repeat. Hack a nugget, nest lists, add parentheses, hack bigger things. But the magic thing where you write code that returns code remained a mystery: we did lots of cool stuff in that course, but we never got to macros.
Until 2026.
The surprise? The surprise is that as each decade passes, I grow to cherish lifelong learning as more and more precious.
-
RE: https://fosstodon.org/@tarsius/116643132796222151
In 1990 Dr. Peter Lee's 15-212 course at #CarnegieMellon introduced me to Scheme. It's also when I first came to comprehend the power of #Emacs and #EmacsLisp.
In the first hour, Professor Lee demonstrated elegantly that everything is a list: data are lists and programs are lists. Every list returns a value, and functions are just lists that do calculations! Functions can return lists, of course, and so you can write functions that return functions!
I ran to the lab to hack Lisp: it wasn't in your pocket, it was in a room worth more than your parents' house. Nothing had ever seemed more natural: write, evaluate, repeat. Hack a nugget, nest lists, add parentheses, hack bigger things. But the magic thing where you write code that returns code remained a mystery: we did lots of cool stuff in that course, but we never got to macros.
Until 2026.
The surprise? The surprise is that as each decade passes, I grow to cherish lifelong learning as more and more precious.
-
RE: https://fosstodon.org/@tarsius/116643132796222151
In 1990 Dr. Peter Lee's 15-212 course at #CarnegieMellon introduced me to Scheme. It's also when I first came to comprehend the power of #Emacs and #EmacsLisp.
In the first hour, Professor Lee demonstrated elegantly that everything is a list: data are lists and programs are lists. Every list returns a value, and functions are just lists that do calculations! Functions can return lists, of course, and so you can write functions that return functions!
I ran to the lab to hack Lisp: it wasn't in your pocket, it was in a room worth more than your parents' house. Nothing had ever seemed more natural: write, evaluate, repeat. Hack a nugget, nest lists, add parentheses, hack bigger things. But the magic thing where you write code that returns code remained a mystery: we did lots of cool stuff in that course, but we never got to macros.
Until 2026.
The surprise? The surprise is that as each decade passes, I grow to cherish lifelong learning as more and more precious.
-
Scriba: a Lisp structured logging framework (Guile Scheme) v0.0.6
https://codeberg.org/jjba23/scriba
Scriba brings modern observability to GNU Guile with zero boilerplate and minimal overhead, amazing configurability and . multiple backends, with support for auto config
#GuileScheme #Lisp #Scheme #GNU #freesoftware #OpenSource #GNU #Observability #Logging #SoftwareDevelopment #log #framework #macro
-
Scriba: a Lisp structured logging framework (Guile Scheme) v0.0.6
https://codeberg.org/jjba23/scriba
Scriba brings modern observability to GNU Guile with zero boilerplate and minimal overhead, amazing configurability and . multiple backends, with support for auto config
#GuileScheme #Lisp #Scheme #GNU #freesoftware #OpenSource #GNU #Observability #Logging #SoftwareDevelopment #log #framework #macro
-
Scriba: a Lisp structured logging framework (Guile Scheme) v0.0.6
https://codeberg.org/jjba23/scriba
Scriba brings modern observability to GNU Guile with zero boilerplate and minimal overhead, amazing configurability and . multiple backends, with support for auto config
#GuileScheme #Lisp #Scheme #GNU #freesoftware #OpenSource #GNU #Observability #Logging #SoftwareDevelopment #log #framework #macro
-
define-typed: efficient typechecks for #Guile Scheme:
https://www.draketo.de/software/guile-define-typeddefine-typed now supports the -> ret style in addition to the structural style:
(define-typed (foo a) (real? -> real?) a) ;; checks a and the returned valueAnd leaving out the return check is now automatically treated as #f (no check):
(define-typed (foo a) (real?) #t) ;; only checks a -
define-typed: efficient typechecks for #Guile Scheme:
https://www.draketo.de/software/guile-define-typeddefine-typed now supports the -> ret style in addition to the structural style:
(define-typed (foo a) (real? -> real?) a) ;; checks a and the returned valueAnd leaving out the return check is now automatically treated as #f (no check):
(define-typed (foo a) (real?) #t) ;; only checks a -
define-typed now supports the -> ret style in addition to the structural style:
(define-typed (foo a) (real? -> real?) a) ;; checks a and the returned value
And leaving out the return check is now automatically treated as #f (no check).
(define-typed (foo a) (real?) #t) ;; only checks a
- code: https://hg.sr.ht/~arnebab/guile-define-typed
- article: https://www.draketo.de/software/guile-define-typed -
define-typed now supports the -> ret style in addition to the structural style:
(define-typed (foo a) (real? -> real?) a) ;; checks a and the returned value
And leaving out the return check is now automatically treated as #f (no check).
(define-typed (foo a) (real?) #t) ;; only checks a
- code: https://hg.sr.ht/~arnebab/guile-define-typed
- article: https://www.draketo.de/software/guile-define-typed -
I, for one, like it that "multiple-value-" is spelled out in full.
This kind of naming convention has advantages.
Myself, I am in a different kind of trouble, trying to remember
which returns multiple values and which returns a list:
`multiple-value-list'
`values-list'By the way, given my ignorance about Scheme, I can't guess _just by the name_ what _either_ of these does, _exactly_:
`and-let*'
`given' -
I, for one, like it that "multiple-value-" is spelled out in full.
This kind of naming convention has advantages.
Myself, I am in a different kind of trouble, trying to remember
which returns multiple values and which returns a list:
`multiple-value-list'
`values-list'By the way, given my ignorance about Scheme, I can't guess _just by the name_ what _either_ of these does, _exactly_:
`and-let*'
`given' -
I, for one, like it that "multiple-value-" is spelled out in full.
This kind of naming convention has advantages.
Myself, I am in a different kind of trouble, trying to remember
which returns multiple values and which returns a list:
`multiple-value-list'
`values-list'By the way, given my ignorance about Scheme, I can't guess _just by the name_ what _either_ of these does, _exactly_:
`and-let*'
`given' -
I, for one, like it that "multiple-value-" is spelled out in full.
This kind of naming convention has advantages.
Myself, I am in a different kind of trouble, trying to remember
which returns multiple values and which returns a list:
`multiple-value-list'
`values-list'By the way, given my ignorance about Scheme, I can't guess _just by the name_ what _either_ of these does, _exactly_:
`and-let*'
`given' -
I, for one, like it that "multiple-value-" is spelled out in full.
This kind of naming convention has advantages.
Myself, I am in a different kind of trouble, trying to remember
which returns multiple values and which returns a list:
`multiple-value-list'
`values-list'By the way, given my ignorance about Scheme, I can't guess _just by the name_ what _either_ of these does, _exactly_:
`and-let*'
`given' -
CW: SRFI-2
I've been a keen user of the "and-let* macro defined in the SRFI-2. I've even authored its sequel, SRFI-202.
But I never really liked the name.
I mean, it does reveal that conceptually it's an amalgam of "and" and "let*. But as a word to be used in a language, it's rather clumsy.(In this regard it resembles "multiple-value-bind" from Common Lisp. OK, it does bind multiple values, but that's not a handy word. It's as if "progn" from Common Lisp was "evaluate-forms-in-order. I mean, "progn" is already a bad name compared to Scheme's "begin", but)
In either case, today I had a small revelation. I mean, I've been thinking about the right name for "and-let*" for many years, so moments like this don't happen very often.
So, ladies and gentlemen, who - like me - are disappointed with the name of the "and-let*" macro, even though you find the macro itself useful, let me present a better alternative:
given
You're welcome.
-
CW: SRFI-2
I've been a keen user of the "and-let* macro defined in the SRFI-2. I've even authored its sequel, SRFI-202.
But I never really liked the name.
I mean, it does reveal that conceptually it's an amalgam of "and" and "let*. But as a word to be used in a language, it's rather clumsy.(In this regard it resembles "multiple-value-bind" from Common Lisp. OK, it does bind multiple values, but that's not a handy word. It's as if "progn" from Common Lisp was "evaluate-forms-in-order. I mean, "progn" is already a bad name compared to Scheme's "begin", but)
In either case, today I had a small revelation. I mean, I've been thinking about the right name for "and-let*" for many years, so moments like this don't happen very often.
So, ladies and gentlemen, who - like me - are disappointed with the name of the "and-let*" macro, even though you find the macro itself useful, let me present a better alternative:
given
You're welcome.
-
CW: SRFI-2
I've been a keen user of the "and-let* macro defined in the SRFI-2. I've even authored its sequel, SRFI-202.
But I never really liked the name.
I mean, it does reveal that conceptually it's an amalgam of "and" and "let*. But as a word to be used in a language, it's rather clumsy.(In this regard it resembles "multiple-value-bind" from Common Lisp. OK, it does bind multiple values, but that's not a handy word. It's as if "progn" from Common Lisp was "evaluate-forms-in-order. I mean, "progn" is already a bad name compared to Scheme's "begin", but)
In either case, today I had a small revelation. I mean, I've been thinking about the right name for "and-let*" for many years, so moments like this don't happen very often.
So, ladies and gentlemen, who - like me - are disappointed with the name of the "and-let*" macro, even though you find the macro itself useful, let me present a better alternative:
given
You're welcome.
-
CW: SRFI-2
I've been a keen user of the "and-let* macro defined in the SRFI-2. I've even authored its sequel, SRFI-202.
But I never really liked the name.
I mean, it does reveal that conceptually it's an amalgam of "and" and "let*. But as a word to be used in a language, it's rather clumsy.(In this regard it resembles "multiple-value-bind" from Common Lisp. OK, it does bind multiple values, but that's not a handy word. It's as if "progn" from Common Lisp was "evaluate-forms-in-order. I mean, "progn" is already a bad name compared to Scheme's "begin", but)
In either case, today I had a small revelation. I mean, I've been thinking about the right name for "and-let*" for many years, so moments like this don't happen very often.
So, ladies and gentlemen, who - like me - are disappointed with the name of the "and-let*" macro, even though you find the macro itself useful, let me present a better alternative:
given
You're welcome.
-
CW: SRFI-2
I've been a keen user of the "and-let* macro defined in the SRFI-2. I've even authored its sequel, SRFI-202.
But I never really liked the name.
I mean, it does reveal that conceptually it's an amalgam of "and" and "let*. But as a word to be used in a language, it's rather clumsy.(In this regard it resembles "multiple-value-bind" from Common Lisp. OK, it does bind multiple values, but that's not a handy word. It's as if "progn" from Common Lisp was "evaluate-forms-in-order. I mean, "progn" is already a bad name compared to Scheme's "begin", but)
In either case, today I had a small revelation. I mean, I've been thinking about the right name for "and-let*" for many years, so moments like this don't happen very often.
So, ladies and gentlemen, who - like me - are disappointed with the name of the "and-let*" macro, even though you find the macro itself useful, let me present a better alternative:
given
You're welcome.
-
Simon Dobson @simoninireland reviewed the Common Lisp Cookbook as part of his Lisp bibliography.
https://simondobson.org/2026/05/22/the-common-lisp-cookbook
Cc @vindarel
-
Simon Dobson @simoninireland reviewed the Common Lisp Cookbook as part of his Lisp bibliography.
https://simondobson.org/2026/05/22/the-common-lisp-cookbook
Cc @vindarel
-
Simon Dobson @simoninireland reviewed the Common Lisp Cookbook as part of his Lisp bibliography.
https://simondobson.org/2026/05/22/the-common-lisp-cookbook
Cc @vindarel
-
Simon Dobson @simoninireland reviewed the Common Lisp Cookbook as part of his Lisp bibliography.
https://simondobson.org/2026/05/22/the-common-lisp-cookbook
Cc @vindarel
-
Simon Dobson @simoninireland reviewed the Common Lisp Cookbook as part of his Lisp bibliography.
https://simondobson.org/2026/05/22/the-common-lisp-cookbook
Cc @vindarel
-
Ryan Burnside wrote SNOW.LISP, a graphics animation program in Interlisp that demonstrates programming techniques such as yielding process control and screen buffering.
-
Ryan Burnside wrote SNOW.LISP, a graphics animation program in Interlisp that demonstrates programming techniques such as yielding process control and screen buffering.
