about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik Agaram2021-06-261-6/+0
| | | | Drop some long-obsolete tooling. I no longer use iTerm2.
* .Kartik Agaram2021-06-241-38/+44
|
* .Kartik Agaram2021-06-24261-8393/+8636
| | | | Switch html rendering to a white background.
* .Kartik Agaram2021-06-241-53/+0
|
* .Kartik Agaram2021-06-241-3/+3
|
* .Kartik Agaram2021-06-245-2/+2
|
* .Kartik Agaram2021-06-241-1/+1
|
* .Kartik Agaram2021-06-234-2/+2
|
* .Kartik Agaram2021-06-231-8/+0
|
* .Kartik Agaram2021-06-231-1/+1
|
* .Kartik Agaram2021-06-231-2/+2
|
* .Kartik Agaram2021-06-2317-5546/+6890
|
* .Kartik Agaram2021-06-231-4/+4
|
* .Kartik Agaram2021-06-231-1/+1
|
* one more bug, and documentation for infixKartik K. Agaram2021-06-234-27/+80
| | | | One error message gets a bit worse.
* .Kartik K. Agaram2021-06-231-3/+3
|
* .Kartik K. Agaram2021-06-231-8/+8
|
* one more bugKartik K. Agaram2021-06-232-9/+22
|
* start using infix in data diskKartik K. Agaram2021-06-231-57/+54
| | | | Still some gaps to track down.
* all tests passing again; infix seems doneKartik K. Agaram2021-06-223-16/+20
|
* infix tests passing but something's still brokenKartik K. Agaram2021-06-221-2/+48
|
* 2 failing tests remainingKartik K. Agaram2021-06-221-2/+44
| | | | We just need to support unary operators.
* almost there; this is encouragingKartik K. Agaram2021-06-221-16/+21
| | | | The at-head-of-list? is a really ugly hack, though.
* beginnings of tokenization within symbolsKartik K. Agaram2021-06-222-17/+68
| | | | We're now down to 4 failing tests. But these will require surgery.
* .Kartik K. Agaram2021-06-222-21/+3
|
* clean up lexical categoriesKartik K. Agaram2021-06-223-142/+58
|
* snapshotKartik K. Agaram2021-06-221-3/+32
| | | | | Still a couple of failing tests before I switch gears to breaking down symbols containing infix.
* .Kartik K. Agaram2021-06-221-3/+5
|
* snapshot: infixKartik K. Agaram2021-06-226-26/+557
| | | | | | | | | | | | | | | | | | | | | Like parenthesize, I'm copying tests over from https://github.com/akkartik/wart Unlike parenthesize, though, I can't just transliterate the code itself. Wart was operating on an intermediate AST representation. Here I'm all the way down to cells. That seemed like a good idea when I embarked, but now I'm not so sure. Operating with the right AST data structure allowed me to more easily iterate over the elements of a list. The natural recursion for cells is not a good fit. This patch and the next couple is an interesting case study in what makes Unix so effective. Yes, you have to play computer, and yes it gets verbose and ugly. But just diff and patch go surprisingly far in helping build a picture of the state space in my brain. Then again, there's a steep gradient of skills here. There are people who can visualize state spaces using diff and patch far better than me, and people who can't do it as well as me. Nature, nurture, having different priorities, whatever the reason. Giving some people just the right crutch excludes others.
* .Kartik K. Agaram2021-06-213-67/+89
|
* start implementing infixKartik K. Agaram2021-06-211-281/+3
| | | | First step: undo operator support in tokenization.
* .Kartik K. Agaram2021-06-201-3/+3
|
* shell: now no definitions with long linesKartik K. Agaram2021-06-201-3/+7
|
* shell: shrink definition widths in a few placesKartik K. Agaram2021-06-201-12/+14
| | | | The only remaining long lines now are in 'pair' and 'with'.
* this is how we create aliasesKartik K. Agaram2021-06-201-1/+1
|
* preserve indentation of the sandboxKartik K. Agaram2021-06-203-7/+7
|
* 'with' lets us drop a few more parensKartik K. Agaram2021-06-201-40/+41
|
* new macro: withKartik K. Agaram2021-06-204-4/+66
|
* new macro: retKartik K. Agaram2021-06-201-6/+7
| | | | http://arclanguage.org/item?id=11068
* start dropping parens everywhereKartik K. Agaram2021-06-201-96/+98
|
* start guessing parentheses based on indentationKartik K. Agaram2021-06-203-77/+66
|
* snapshotKartik K. Agaram2021-06-208-22/+591
| | | | | This is going better than expected; just 3 failing tests among the new ones.
* start emitting indent tokensKartik K. Agaram2021-06-185-31/+227
|
* redo next-token in more high-level termsKartik K. Agaram2021-06-182-73/+95
|
* .Kartik K. Agaram2021-06-181-30/+30
|
* .Kartik K. Agaram2021-06-181-49/+49
|
* start emitting token for newlineKartik K. Agaram2021-06-181-5/+12
|
* newlines are now a tokenKartik K. Agaram2021-06-182-4/+12
|
* start implementing indent-sensitivityKartik K. Agaram2021-06-181-2/+26
| | | | | | | General plan: stop skipping newlines during tokenization introduce a new indent token, initially skip it transparently start doing cleverer things
* .Kartik K. Agaram2021-06-181-6/+2
|