| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
snapshot: migrating call-path to store word handles rather than word indexes.
ctrl-a and ctrl-e are segfaulting. There are likely other problems.
The major new change here is that allocating a call-path-element no longer
initializes it.
|
| |
|
|
| |
A new example that better demonstrates the value of named arguments.
|
| | |
|
| |
|
|
|
|
|
| |
I just needed to remove an obsolete guardrail in render-line.
Still seeing some bugs with left-arrow when playing around with the full
expansion of `1 2+`.
|
| |
|
|
|
| |
Bring back definitions for 1+ and 2+. Expanding nested calls still doesn't
work.
|
| |
|
|
|
|
|
| |
Starting to work. I'm still seeing problems in lines with multiple expanded
calls, but perhaps that's a rendering issue.
The code is absolutely ghastly.
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| |
|
|
|
|
| |
Emit a stack of not ints but more complex objects containing the int payload.
Function calls again segfaulting.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
I actually deleted a test here! Hard-core prototype mode.
|