about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* shell: raise errors when loading code on bootKartik K. Agaram2021-05-302-16/+29
|
* bugfix: unbound variables were not raising errorKartik K. Agaram2021-05-306-8/+40
| | | | | Since we switched error trace semantics from a designated label to a designated depth (commit 9831a8cef9 on May 19).
* .Kartik K. Agaram2021-05-301-3/+3
|
* unconditionally trace errorsKartik K. Agaram2021-05-301-60/+0
| | | | | | Now that we never have a null trace, tracing errors is always safe. And now that we're running with low trace max-depth we're more likely to run into problems with missing errors in the trace.
* .Kartik K. Agaram2021-05-301-0/+5
|
* .Kartik K. Agaram2021-05-301-1/+1
|
* first test re-running sandbox with a deeper traceKartik K. Agaram2021-05-302-3/+75
|
* .Kartik K. Agaram2021-05-301-10/+10
|
* .Kartik K. Agaram2021-05-301-1/+47
|
* first attempt doesn't workKartik K. Agaram2021-05-302-0/+38
| | | | | | I was aware of some complications. The various indexes and y coordinates in the trace's cache would be unstable and need to be recomputed. But it's surprising that the trace _completely disappears_.
* start progressively increasing trace depthKartik K. Agaram2021-05-301-24/+30
| | | | | | | | | | | The goal: the sandbox initially maintains a shallow trace. As you expand into the trace, the environment reruns the sandbox at greater depth as needed. The challenge: expanding happens within edit-trace, which doesn't have the whole sandbox needed to re-run the sandbox. We'll either need to expand the trace's capabilities to include the whole sandbox, or duplicate some logic to decide when to run the sandbox.
* .Kartik K. Agaram2021-05-291-4/+45
|
* .Kartik K. Agaram2021-05-291-82/+54
|
* shell: scrolling the traceKartik K. Agaram2021-05-292-4/+211
|
* fix a bug in loading code diskKartik K. Agaram2021-05-291-1/+1
| | | | Identical bug to commit 2f10bc7302.
* shell: skeleton for scrollingKartik K. Agaram2021-05-294-4/+44
|
* cache visibility for all lines in traceKartik K. Agaram2021-05-291-15/+35
| | | | | | 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.
* .Kartik K. Agaram2021-05-291-4/+5
|
* .Kartik K. Agaram2021-05-291-1/+1
|
* .Kartik K. Agaram2021-05-291-1/+1
|
* .Kartik K. Agaram2021-05-291-1/+1
|
* shell: start implementing scrolling in the traceKartik K. Agaram2021-05-291-0/+1
| | | | | | | | | | | | | 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.
* .Kartik K. Agaram2021-05-291-0/+2
|
* .Kartik K. Agaram2021-05-291-0/+1
|
* shell: non-stream tokens are now smallKartik K. Agaram2021-05-291-3/+11
|
* .Kartik K. Agaram2021-05-291-6/+4
|
* .Kartik K. Agaram2021-05-291-9/+10
|
* .Kartik K. Agaram2021-05-291-4/+4
|
* .Kartik K. Agaram2021-05-291-2/+0
|
* .Kartik K. Agaram2021-05-291-10/+10
|
* .Kartik K. Agaram2021-05-291-12/+12
|
* shell: start reducing the waste in tokenizeKartik K. Agaram2021-05-291-11/+11
|
* .Kartik K. Agaram2021-05-292-0/+34
| | | | | 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.
* .Kartik K. Agaram2021-05-231-5/+9
| | | | slightly improve colors
* ctrl-s in trace: show entire current lineKartik K. Agaram2021-05-231-7/+55
|
* .Kartik K. Agaram2021-05-231-1/+1
|
* disable ctrl-s when browsing traceKartik K. Agaram2021-05-232-6/+12
| | | | | We're soon going to be dynamically rerunning the sandbox in other ways when browsing the trace.
* .Kartik K. Agaram2021-05-231-4/+4
|
* shrink trace menuKartik K. Agaram2021-05-231-8/+2
|
* start truncating trace linesKartik K. Agaram2021-05-232-6/+6
|
* .Kartik Agaram2021-05-232-2/+2
|
* .Kartik Agaram2021-05-232-19/+1
|
* shell: reduce trace depth in sandboxKartik K. Agaram2021-05-223-1/+24
| | | | We'll gradually make this more dynamic.
* .Kartik K. Agaram2021-05-221-1/+1
|
* .Kartik Agaram2021-05-201-2/+4
|
* .Kartik K. Agaram2021-05-192-3/+13
|
* a second place with lousy storage managementKartik K. Agaram2021-05-192-4/+17
|
* more robust print-cellKartik K. Agaram2021-05-194-20/+254
| | | | | It is used to print to the trace, and we shouldn't crash the whole computer just because the trace ran out of space.
* disallow null tracesKartik K. Agaram2021-05-198-153/+425
| | | | | | We now use traces everywhere for error-checking. Null traces introduce the possibility of changing a functions error response, and therefore its semantics.
* .Kartik K. Agaram2021-05-191-1/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-30 16:40:33 +0000