Liskell – Haskell Semantics with Lisp Syntax [pdf]
Key topics
The debate around Liskell, a language blending Haskell's semantics with Lisp's syntax, sparked a lively discussion on the role of macros in programming languages. Some commenters argued that Haskell's laziness largely replaces the need for macros, while others countered that typeclasses are no substitute for proper macros. The conversation also veered into related projects, such as Hackett and Coalton, which similarly experiment with combining Haskell and Lisp features, and comparisons were drawn with other languages like Shen and Rust. As the discussion unfolded, it became clear that the search for the perfect blend of functional programming and macro capabilities remains an active area of exploration.
Snapshot generated from the HN discussion
Discussion Activity
Active discussionFirst comment
23h
Peak period
12
18-24h
Avg / period
6.3
Based on 25 loaded comments
Key moments
- 01Story posted
Dec 15, 2025 at 4:41 PM EST
18 days ago
Step 01 - 02First comment
Dec 16, 2025 at 3:32 PM EST
23h after posting
Step 02 - 03Peak activity
12 comments in 18-24h
Hottest window of the conversation
Step 03 - 04Latest activity
Dec 19, 2025 at 1:15 PM EST
15 days ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
No. Typeclasses do not replace proper macros. Go home, you are drunk.
[0] https://www.reddit.com/r/haskell/comments/5xge0v/comment/deh...
[1] https://www.reddit.com/r/haskell/comments/1929xn/comment/c8k...
https://augustss.blogspot.com/2011/05/more-points-for-lazy-e...
Chastised, Anton took his leave from his master and returned to his cell, intent on studying closures. He carefully read the entire "Lambda: The Ultimate..." series of papers and its cousins, and implemented a small Scheme interpreter with a closure-based object system. He learned much, and looked forward to informing his master of his progress.
On his next walk with Qc Na, Anton attempted to impress his master by saying Master, I have diligently studied the matter, and now understand that objects are truly a poor man's closures." Qc Na responded by hitting Anton with his stick, saying "When will you learn? Closures are a poor man's object."
At that moment, Anton became enlightened.
github repo: https://github.com/lexi-lambda/hackett
Documentation: https://lexi-lambda.github.io/hackett/
Rust semantics with D syntax (garbage collector is a bonus).
The big news is that this will cover the GC cases too, not only the manual memory management.
> Coalton is an efficient, statically typed functional programming language that supercharges Common Lisp.
Presentation this year on the ELS: https://www.youtube.com/watch?v=of92m4XNgrM
Edit: I think I see what you mean now. Lisp backend vs Haskell backend.
Anyway, Coalton is a joy to use and IMO a breath of fresh air in CL. It's quite easy start using as a library; go all-in or only use it in specific parts of the code. It's great to be able to choose between (or intermix)the flexibility of CL and the guarantees of a statically typed language (as well as some nice performance boosts with arguably less work). Some aspects are still young (some of the standard library, ecosystem, editor support), but it's quite thoughtfully crafted and I'm excited to see where it goes.
Not exactly. Coalton brings ML-style strong typing to Common Lisp. But Coalton code is also Lisp code.
The backend, thus, is Common Lisp, and it is available at all times, thus leveraging all its power.
https://shenlanguage.org
https://shen-language.github.io
It took a while to click through a link to an actual implementation on github, which had some test examples. None of which were documented.
So idk? I'm not going to buy the ebook for $41 to find out.
So to answer your original question: Liskell, despite being 13 years old and unmaintained, does actually have an accessible document that _explains what it is_.
Which is a strength in some aspects, and, although many lispers will never admit it, a weakness in others.