| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
We stopped rendering just the widget under focus when we switched away
from the simplistic list of editors. Need to bring that back.
|
| |
|
|
|
| |
Profiling shows the bulk of time is spent in read_memory, canonize,
absolutize. But I'm not sure how to optimize those places.
|
| |
|
|
|
|
|
|
|
| |
Speeds up edit.mu tests by 10x, and shrinks memory usage by 100x.
We need a more efficient implementation of traces, but we can keep going
for now.
We didn't really need to reclaim memory just yet, after all. Mu is
pretty memory-efficient.
|
| |
|
|
|
| |
I keep forgetting about it. Until, that is, I run gprof. Even if I think
I need a memory profile, a cpu profile is a pretty good proxy.
|
| |
|
|
|
|
| |
But still no difference in either memory footprint or in running time.
This will teach me -- for the umpteenth time -- to optimize before
measuring.
|
| |
|
|
|
|
| |
Now we can reclaim allocated space. But the API's suspect. I still want
to provide some sort of tree of allocations. For now we'll use this only
to reclaim default-spaces. That's next.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Turns out to not affect memory utilization or run-time. At all.
But still looks nicer and requires less fudging on our part.
|
| |
|
|
| |
Let's see how much this helps edit.mu.
|
| | |
|
| |
|
|
| |
We won't bother supporting names for globals, for now.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
As usual, trying to fix this manually was a false economy. Writing this
test in the first place would have made debugging much simpler.
|
| |
|
|
| |
Finally, albeit too late for my demo.
|
| | |
|
| |
|
|
| |
Quick hack for demo at balisp meetup today.
|
| |
|
|
| |
No idea why this was wrong, but whatever..
|
| |
|
|
|
|
|
|
|
| |
We're starting to hit the limits of my 8GB RAM, to the point where I'm
starting to economize on the size of the screen. Time to start thinking
about reclaiming memory.
Anyways, test now fails in the right place. I'm failing to propertly
render intermediate lines between sandboxes.
|
| | |
|
| |
|
|
| |
We're ready to start displaying multiple sandboxes.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Cleanup below editors is now all done.
|
| | |
|
| |
|
|
|
|
|
| |
Ah, I was indeed double-rendering, but somehow it was still hard to see
the problem past that preliminary diagnosis.
Still two failing tests to fix.
|
| |
|
|
|
| |
No, that's a false alarm. There's just a larger screen to manipulate.
But the size of the screen doesn't change in interactive mode.
|
| |
|
|
|
|
| |
Comparing trace counts for a single test before and after yesterday's
changes, one obvious culprit is that print-character has blown up from
754 trace lines (at all levels) to 2554.
|
| | |
|
| | |
|
| |
|
|
| |
$ ./mu test run-instruction-and-print-warnings
|
| |
|
|
|
|
|
|
|
|
| |
Still ugly as hell. Some tests failing, but they're most likely
wrong. We need to test cursor positioning at the level of the
environment and take it away from the responsibilities of individual
editors. Also bring back the line at the bottom of each editor.
The non-test run ('main' in edit.mu) is completely borked. Sluggish as
hell, and I can't seem to switch focus to the sandbox editor.
|
| |
|
|
|
| |
Current model: you click on something to put it on the editor at the top
of the column. Worth a shot.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
I probably need another test like editor-clears-last-line-on-backspace,
but we aren't testing the boundary, and we're pushing on anyway.
|
| |
|
|
| |
Leaves a line blank after printing result/warnings, for some reason.
|
| | |
|
| | |
|
| |
|
|
| |
All tests passing, but early layers are broken.
|