about summary refs log tree commit diff stats
path: root/apps/tile
Commit message (Collapse)AuthorAgeFilesLines
* 7222Kartik Agaram2020-11-103-43/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ok, I found a failing manual test for files as well. Here are the two steelman tests, one for screens and one for files: 1. 5 5 fake-screen =s s 1 down 1 right ctrl-d foo expand final state: s foo foo s 1 down 1 right ⇗ ┌─────┐ ┌─────┐ ┌─────┐ 1 ┌─────┐ 1 ┌─────┐ │ ┌─────┐ │ ┌─────┐ │ ─ │ │ │ │ ─ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ 2. "x" open =f f read f read ctrl-d read2 expand final state: f read2 read2 f read f read ⇗ FILE ❝def❞ FILE ❝abc❞ FILE ❝❞ ❝def❞ ❝ghi❞ In both cases there are 3 levels of issues: - getting a single-line expression to work - getting a single-line expression to work when operating on a binding defined in a previous line - getting an expanded function call to work The third is where the rub is right now. And what both examples above share is that the function performs 2 mutations to the screen/file. So we need a deep copy after all. And it's not very clear how to copy a file descriptor including the seek location. Linux's dup() syscall creates an alias to the file descriptor. And opening /proc seems awfully Linux-specific: https://stackoverflow.com/questions/54727231/duplicating-file-descriptor-and-seeking-through-both-of-them-independently/54727424#54727424
* 7221Kartik Agaram2020-11-091-62/+0
| | | | | I can't get file values to exhibit the same problem. Why are fake screens special?
* 7220Kartik Agaram2020-11-091-5/+12
| | | | | | | | | Even this isn't enough. While shallow copies keep us from transferring new bindings to callers, the screen object is still the same, so mutations to bindings are contagious. Basically I'm losing IQ points from programming in a language that encourages mutation over copying.
* 7219Kartik Agaram2020-11-093-69/+69
| | | | We're still busted, but on the right track.
* 7218Kartik Agaram2020-11-095-11/+139
| | | | | | | | | | | | | | | This bug was incredibly painful to track down: the one-line fix is to replace 'line' with 'first-line' in the call to 'evaluate' in render-line before recursing. Things that made it challenging: - A high degree of coiling with recursive calls and multiple places of evaluation. - An accidental aliasing in bindings (when rendering the main column in render-line) that masked the underlying bug and made things seem to work most of the time. - Too many fucking arguments to render-line, a maze of twisty line objects all alike.
* 7215Kartik Agaram2020-11-072-2/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Attempt #3: always create a copy of the bindings before each column/evaluate. The details are fuzzy in my head, but it seemed worth trying. I figured I'd either see the old duplication behavior or everything will work. Instead I'm seeing new problems. commit 7208: 5 5 fake-screen =s s 1 down 1 right expected: | - observed: | | - commit 7210-7212: 5 5 fake-screen =s s 1 down 1 right [define foo] s foo [expand foo] observed: no bindings available when rendering foo expanded commit 7213: 5 5 fake-screen =s s 1 down 1 right [define foo] s foo [expand foo] expected within foo: | - observed within foo: | | - commit 7215: 5 5 fake-screen =s s 1 down 1 right [define foo] s foo [expand foo] observed: no bindings available when rendering foo expanded
* 7214 - undo 7213Kartik Agaram2020-11-072-5/+7
| | | | | | | | | | Turns out even that doesn't work. There are two distinct use cases here: 1. Keeping columns from infecting each other. 2. Expanding function calls. Perhaps ping-ponging between them is a sign I need tests.
* 7213 - redo the bugfix of 7210Kartik Agaram2020-11-072-7/+5
| | | | | | | | It turns out deciding when to initialize the table of bindings is quite a thorny problem in the presence of function calls (since they need their args bound). In time I should probably support a linked list of tables. For now I'll just continue to reuse tables, but perform lookups in reverse order so that the correct binding is always returned.
* 7212Kartik Agaram2020-11-071-1/+1
|
* 7211Kartik Agaram2020-11-071-0/+24
|
* 7210Kartik Agaram2020-11-074-11/+40
| | | | | Bug fixed; I had to reinitialize the table of bindings. Interesting debugging experience.
* 7209Kartik Agaram2020-11-071-1/+1
|
* 7208 - tile: start new lineKartik Agaram2020-11-071-0/+35
| | | | | | | | Only the final line shows the stack for now. No way to move cursor back up. One bug I'm noticing: creating a screen on one line and then reusing it in a second causes operations to be performed multiple times.
* 7207 - tile: bugfixKartik Agaram2020-11-071-0/+2
|
* 7206 - tile: up/down/left/right now print linesKartik Agaram2020-11-071-20/+57
|
* 7205 - tile: magnitudes for up/down/left/rightKartik Agaram2020-11-071-17/+41
|
* 7202 - rendering screens above other valuesKartik Agaram2020-11-062-1/+26
|
* 7201Kartik Agaram2020-11-061-8/+6
|
* 7200 - tile: cursor movement helpersKartik Agaram2020-11-062-3/+121
|
* 7199 - tile: primitive 'move'Kartik Agaram2020-11-061-1/+30
|
* 7198 - tile: primitive 'print'Kartik Agaram2020-11-063-6/+43
|
* 7197 - tile: render screen contents and cursorKartik Agaram2020-11-061-10/+38
|
* 7196 - tile: render empty screenKartik Agaram2020-11-062-19/+80
|
* 7195 - tile: create 'screen' objectsKartik Agaram2020-11-064-0/+61
|
* 7194Kartik Agaram2020-11-062-45/+51
|
* 7193 - tile: extract taxonomy of values into a separate fileKartik Agaram2020-11-063-206/+208
|
* 7181 - type checks for 'address' instructionKartik Agaram2020-11-051-2/+2
|
* 7180Kartik Agaram2020-11-041-1/+1
| | | | | | | More bugfixes, now all apps are working. In the process of fixing the bugs in translating apps/browse, I found a typo in apps/tile that just happened to accidentally be compiling fine.
* 7166Kartik Agaram2020-11-031-42/+40
|
* 7165Kartik Agaram2020-11-031-1/+1
| | | | | All tasks of https://github.com/akkartik/mu/issues/45#issuecomment-719990879 should now be complete.
* 7159 - explicitly use 'return' everywhereKartik Agaram2020-11-0211-399/+360
| | | | https://github.com/akkartik/mu/issues/45#issuecomment-719990879, task 2.
* 7156Kartik Agaram2020-11-011-2/+2
|
* 7140Kartik Agaram2020-10-291-0/+11
|
* 7129 - tile: allow bindings anywhereKartik Agaram2020-10-271-7/+7
| | | | | | | | | | Amazing how easy this was. And it does feel more intuitive. If I decide at some point that I want to bind something to a name I don't usually want to lose the entire line after that point. It also sidesteps for now the thorny question of whether to permit organically switching to a new line (rather than using the 'name value' hotkey), and how that should work.
* 7128Kartik Agaram2020-10-271-5/+11
| | | | More consistent spacing in sandbox render.
* 7127Kartik Agaram2020-10-271-1/+1
|
* 7126Kartik Agaram2020-10-271-5/+5
|
* 7125 - tile: fade out values on the stackKartik Agaram2020-10-271-4/+1
|
* 7124 - tiles: better 'lines' primitiveKartik Agaram2020-10-272-14/+19
|
* 7123 - tile: truncate string if necessaryKartik Agaram2020-10-263-3/+30
|
* 7122 - tile: styling for stringsKartik Agaram2020-10-261-1/+6
|
* 7121Kartik Agaram2020-10-261-5/+11
| | | | | | | Starting to polish 'line-count' demo: filename line-count = filename open lines len
* 7120 - tile: array of lines from fileKartik Agaram2020-10-263-1/+77
| | | | Requires a quick hacky change to Mu compiler.
* 7119 - tile: new primitive to slurp file contentsKartik Agaram2020-10-262-1/+41
| | | | | Stack display is messed up when file contents contain newlines. Ignoring that for now.
* 7118Kartik Agaram2020-10-261-3/+5
|
* 7117Kartik Agaram2020-10-261-2/+4
|
* 7116 - tile: regression in typing in stringsKartik Agaram2020-10-262-55/+46
| | | | We really need to clean up the Mu compiler's logic around function outputs.
* 7115Kartik Agaram2020-10-262-6/+6
|
* 7113Kartik Agaram2020-10-261-2/+12
|
* 7112 - tile: arrays of non-integersKartik Agaram2020-10-264-73/+125
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-23 09:22:13 +0000
e>