HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
robpike
lisp
Go2020–2020
robpike / lisp

lisp

Toy Lisp 1.5 interpreter

3Distinct people
3Mentions
0Explicit recommenders
1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Toy Lisp 1.5 interpreter

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval3 dated mentions

Observed mentions: 2020-06-17 07:02:01 UTC to 2020-06-23 03:49:43 UTC.

012020-06-17 06:00:00 UTC to 2020-06-17 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 17, 06:002020-06-17 12:00:00 UTC to 2020-06-17 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-06-17 18:00:00 UTC to 2020-06-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-18 00:00:00 UTC to 2020-06-18 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-18 06:00:00 UTC to 2020-06-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-18 12:00:00 UTC to 2020-06-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-18 18:00:00 UTC to 2020-06-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 00:00:00 UTC to 2020-06-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 06:00:00 UTC to 2020-06-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 12:00:00 UTC to 2020-06-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 18:00:00 UTC to 2020-06-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 00:00:00 UTC to 2020-06-20 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 20, 00:002020-06-20 06:00:00 UTC to 2020-06-20 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 12:00:00 UTC to 2020-06-20 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 18:00:00 UTC to 2020-06-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 00:00:00 UTC to 2020-06-21 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 06:00:00 UTC to 2020-06-21 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 12:00:00 UTC to 2020-06-21 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 18:00:00 UTC to 2020-06-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-22 00:00:00 UTC to 2020-06-22 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-22 06:00:00 UTC to 2020-06-22 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-22 12:00:00 UTC to 2020-06-22 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-22 18:00:00 UTC to 2020-06-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-23 00:00:00 UTC to 2020-06-23 06:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 23, 00:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 17, 06:002020-06-17 06:00:00 UTC2020-06-17 12:00:00 UTC110
Jun 17, 12:002020-06-17 12:00:00 UTC2020-06-17 18:00:00 UTC101
Jun 17, 18:002020-06-17 18:00:00 UTC2020-06-18 00:00:00 UTC000
Jun 18, 00:002020-06-18 00:00:00 UTC2020-06-18 06:00:00 UTC000
Jun 18, 06:002020-06-18 06:00:00 UTC2020-06-18 12:00:00 UTC000
Jun 18, 12:002020-06-18 12:00:00 UTC2020-06-18 18:00:00 UTC000
Jun 18, 18:002020-06-18 18:00:00 UTC2020-06-19 00:00:00 UTC000
Jun 19, 00:002020-06-19 00:00:00 UTC2020-06-19 06:00:00 UTC000
Jun 19, 06:002020-06-19 06:00:00 UTC2020-06-19 12:00:00 UTC000
Jun 19, 12:002020-06-19 12:00:00 UTC2020-06-19 18:00:00 UTC000
Jun 19, 18:002020-06-19 18:00:00 UTC2020-06-20 00:00:00 UTC000
Jun 20, 00:002020-06-20 00:00:00 UTC2020-06-20 06:00:00 UTC000
Jun 20, 06:002020-06-20 06:00:00 UTC2020-06-20 12:00:00 UTC000
Jun 20, 12:002020-06-20 12:00:00 UTC2020-06-20 18:00:00 UTC000
Jun 20, 18:002020-06-20 18:00:00 UTC2020-06-21 00:00:00 UTC000
Jun 21, 00:002020-06-21 00:00:00 UTC2020-06-21 06:00:00 UTC000
Jun 21, 06:002020-06-21 06:00:00 UTC2020-06-21 12:00:00 UTC000
Jun 21, 12:002020-06-21 12:00:00 UTC2020-06-21 18:00:00 UTC000
Jun 21, 18:002020-06-21 18:00:00 UTC2020-06-22 00:00:00 UTC000
Jun 22, 00:002020-06-22 00:00:00 UTC2020-06-22 06:00:00 UTC000
Jun 22, 06:002020-06-22 06:00:00 UTC2020-06-22 12:00:00 UTC000
Jun 22, 12:002020-06-22 12:00:00 UTC2020-06-22 18:00:00 UTC000
Jun 22, 18:002020-06-22 18:00:00 UTC2020-06-23 00:00:00 UTC000
Jun 23, 00:002020-06-23 00:00:00 UTC2020-06-23 06:00:00 UTC110

What Hacker News says

3 sources
Interesting: https://github.com/robpike/lisp/blob/master/lisp1_5/parse.go... // Expr represents an arbitrary expression. type Expr struct { // An Expr is either an atom, with atom set, or a list, with car and cdr set. // Car and cdr can be nil (empty) even if atom is nil. car *Expr atom *token cdr *Expr } Instead of using interface types for expressions, there is a simple expression structure type with fields that may or may not be set depending on what type of value it is. I probably never would have done it that way, I would probably use an interface type instead. This way actually saves space in cons objects… in the above version, a cons is 24 bytes, and below it would be 32: type Expr interface { } type Cons struct { car, cdr Expr } Not efficient compared to modern Lisp i
Read the rest
nterpretations, but an interesting choice.
In Robpike/Lisp: Toy Lisp 1.5 interpreter in Go

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.