Kartik K. Agaram
1d89aa38c2
fix a bug in loading code disk
...
Identical bug to commit 2f10bc7302
.
2021-05-29 18:43:16 -07:00
Kartik K. Agaram
9516dfa0b0
shell: skeleton for scrolling
2021-05-29 17:23:04 -07:00
Kartik K. Agaram
d85529f3fa
cache visibility for all lines in trace
...
So far we were only doing so for the first few lines, just enough to render
one page's worth of lines. We'd have probably noticed if we collapsed some
lines after re-evaluating.
2021-05-29 17:13:06 -07:00
Kartik K. Agaram
fde296ca3c
.
2021-05-29 17:03:22 -07:00
Kartik K. Agaram
58c801db0f
.
2021-05-29 16:49:36 -07:00
Kartik K. Agaram
af46771821
.
2021-05-29 16:42:15 -07:00
Kartik K. Agaram
91ddc3a82d
.
2021-05-29 16:41:47 -07:00
Kartik K. Agaram
c8b2424f45
shell: start implementing scrolling in the trace
...
I've been stymied for a week wondering how to reliably compute trace-line
identity. A trace can have multiple identical lines. Only some of them
may be visible at any point. How to remember which is which across re-evaluations?
There's no easy answer. I'm just going to keep things ad hoc. When you
re-evaluate, new lines can currently pop into visibility. However we guarantee
that just moving around the trace will be stable, thanks to the visible
bit being cached within each trace-line. Scrolling will be similar. Reevaluating
may cause the trace to be perturbed up or down. However, just scrolling
around will work reliably.
2021-05-29 16:37:32 -07:00
Kartik K. Agaram
4de6f80334
.
2021-05-29 16:25:38 -07:00
Kartik K. Agaram
9b131ce02b
.
2021-05-29 16:22:08 -07:00
Kartik K. Agaram
7b84872380
shell: non-stream tokens are now small
2021-05-29 16:07:39 -07:00
Kartik K. Agaram
0bba6ccfc2
.
2021-05-29 16:04:30 -07:00
Kartik K. Agaram
aceb526b50
.
2021-05-29 16:01:50 -07:00
Kartik K. Agaram
c2e59bbf9d
.
2021-05-29 16:00:59 -07:00
Kartik K. Agaram
6b212ed6e7
.
2021-05-29 15:54:41 -07:00
Kartik K. Agaram
d8f306c30c
.
2021-05-29 15:53:31 -07:00
Kartik K. Agaram
2ad0a98f94
.
2021-05-29 15:53:21 -07:00
Kartik K. Agaram
56c621b6f1
shell: start reducing the waste in tokenize
2021-05-29 15:49:58 -07:00
Kartik K. Agaram
8dc3c85a03
.
...
Minor counter infrastructure. We invoke next-token 1400 times while loading
the shell's data disk, so we're wasting around 1.4MB during tokenization.
2021-05-29 15:40:58 -07:00
Kartik K. Agaram
210553ac68
.
...
slightly improve colors
2021-05-23 22:53:54 -07:00
Kartik K. Agaram
bda55a3eec
ctrl-s in trace: show entire current line
2021-05-23 22:47:40 -07:00
Kartik K. Agaram
f32e8035c7
.
2021-05-23 22:26:49 -07:00
Kartik K. Agaram
7fa0163941
disable ctrl-s when browsing trace
...
We're soon going to be dynamically rerunning the sandbox in other ways
when browsing the trace.
2021-05-23 22:18:51 -07:00
Kartik K. Agaram
d3103378c5
.
2021-05-23 22:17:05 -07:00
Kartik K. Agaram
d474128db1
shrink trace menu
2021-05-23 22:07:50 -07:00
Kartik K. Agaram
b2dd7e6a91
start truncating trace lines
2021-05-23 22:04:31 -07:00
Kartik Agaram
0f5b9a1534
.
2021-05-23 08:06:03 -07:00
Kartik Agaram
49f7a91704
.
2021-05-23 07:55:09 -07:00
Kartik K. Agaram
7a04c8104d
shell: reduce trace depth in sandbox
...
We'll gradually make this more dynamic.
2021-05-22 10:28:21 -07:00
Kartik K. Agaram
6934f78e97
.
2021-05-22 09:30:11 -07:00
Kartik Agaram
cef24e3c85
.
2021-05-20 00:54:21 -07:00
Kartik K. Agaram
64d3e8e2e0
.
2021-05-19 23:32:16 -07:00
Kartik K. Agaram
119e661f20
a second place with lousy storage management
2021-05-19 23:23:49 -07:00
Kartik K. Agaram
4b57c101b7
more robust print-cell
...
It is used to print to the trace, and we shouldn't crash the whole computer
just because the trace ran out of space.
2021-05-19 23:14:27 -07:00
Kartik K. Agaram
e2ab1b30b1
disallow null traces
...
We now use traces everywhere for error-checking. Null traces introduce
the possibility of changing a functions error response, and therefore its
semantics.
2021-05-19 20:56:37 -07:00
Kartik K. Agaram
6bbeadecaa
.
2021-05-19 19:55:29 -07:00
Kartik K. Agaram
f8c28e3a36
.
2021-05-19 17:30:25 -07:00
Kartik K. Agaram
831e2e0d64
.
2021-05-19 17:29:17 -07:00
Kartik K. Agaram
ec2dab7801
shell: traces track a maximum depth to record
2021-05-19 01:26:25 -07:00
Kartik K. Agaram
9831a8cef9
shell: depth 0 as the check for errors
2021-05-19 01:21:02 -07:00
Kartik K. Agaram
3fc03a98e5
shell: start traces at depth 1 rather than 0
...
We're going to carve out depth 0 for errors.
2021-05-19 01:15:35 -07:00
Kartik K. Agaram
91b7b0be73
shell: clean up trace for macroexpand
2021-05-18 20:01:11 -07:00
Kartik K. Agaram
837926751a
shell: add a lot of error-checking
2021-05-18 20:01:11 -07:00
Kartik Agaram
6934436de9
.
2021-05-18 13:09:30 -07:00
Kartik Agaram
5396e24cba
.
2021-05-18 13:04:33 -07:00
Kartik K. Agaram
b4c0b12542
.
2021-05-18 10:25:37 -07:00
Kartik K. Agaram
fd57c48c60
start double-buffering
...
Amazing how much difference it makes even when the implementation is so
naive and slow.
2021-05-18 10:23:54 -07:00
Kartik Agaram
2952a29960
some tweaks for demo on a Mac
2021-05-17 22:21:07 -07:00
Kartik Agaram
06e429cdaf
.
2021-05-17 22:07:51 -07:00
Kartik K. Agaram
ad60a3dece
preserve atemporal state when restarting time
2021-05-17 21:44:24 -07:00