| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Rendering is still ugly. Cursor isn't on the right row. But the hard part
is behind us.
This was a stupid mistake in function-body, and it happened because I've
been getting lazy and passing (addr handle) objects when I should be passing
in "constant" addr objects.
I'm not sure why I was so resistant to debugging by print here. I spent
3 days waffling about with this bug.
|
|
|
|
| |
Tile: simplify the contract for render-column.
|
|
|
|
| |
Changing tack..
|
|
|
|
|
| |
Use the fake-screen infrastructure we already have for non-interactive
mode.
|
|
|
|
|
|
| |
We don't have tests yet in the tile prototype, mostly because we don't
yet feel confident about what desired behavior should be. But it's still
helpful to have a non-interactive mode for tracking down segfaults.
|
|
|
|
|
| |
Snapshot. We've gotten arrow keys navigating, but segfault when getting
to the second word in an expanded function call body.
|
| |
|
| |
|
| |
|
|
|
|
| |
Rather surprisingly, this transformation worked the first time!
|
|
|
|
| |
Fix and cleanup.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Snapshot that requires a check in the Mu compiler.
Currently I don't spill a register if it could possibly be over-written
by a function output within. However, find-in-call-path is a good example
of where this constraint is too lenient and results in unsafe code. The
variable `curr` gets clobbered during loop update by the variable `match?`.
What's the answer? Perhaps we should ban all conditional updates to function
outputs? That'd be dashed inconvenient.
|
|
|
|
|
| |
Function expand/contract still works, but the implementation is totally
different under the hood.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Slowly hoist cursor-word from environment to sandbox. This isn't its final
destination.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We need the state of the stack at the call-site. But rendering is already
working surprisingly well.
|
|
|
|
| |
Extract a new function.
|
| |
|
|
|
|
| |
Track just whether to step inside or not.
|
|
|
|
| |
Back to commit 6872.
|
|
|
|
|
| |
Snapshot. Caching subsidiary stacks is a dead end; they're just the final
iteration. We need to render all iterations.
|
| |
|
|
|
|
| |
Now saving the subsidiary stack.
|
|
|
|
| |
Hackily show function definition.
|
|
|
|
| |
Segfault now fixed. Everything seems to be working again.
|
|
|
|
|
|
| |
Emit a stack of not ints but more complex objects containing the int payload.
Function calls again segfaulting.
|
| |
|
|
|
|
| |
First function call working in apps/tile!
|
|
|
|
| |
Segfault fixed. This shouldn't have been so hard.
|
| |
|
| |
|
|
|
|
|
| |
Snapshot: tile currently segfaulting. I need to back up and make it easier
to debug.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Get rid of cutesy justify thresholds. They didn't actually save me any
trouble, and they won't generalize to other literals besides ints.
|
| |
|
| |
|
| |
|
| |
|