| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
See `cannot_write_tests_for`.
|
| |
|
|
|
|
|
|
|
|
|
| |
It also seems useful that the number maps to the name of the file the
sandbox is saved in. However this mapping is currently a happy accident
and not actually tested.
I'm starting to switch gears and help make the editor useable with
many many sandboxes. This is just the first step of several.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the one major refinement on the C programming model I'm planning
to introduce in mu. Instead of Rust's menagerie of pointer types and
static checking, I want to introduce just one new type, and use it to
perform ref-counting at runtime.
So far all we're doing is updating new's interface. The actual
ref-counting implementation is next.
One implication: I might sometimes need duplicate implementations for a
recipe with allocated vs vanilla addresses of the same type. So far it
seems I can get away with just always passing in allocated addresses;
the situations when you want to pass an unallocated address to a recipe
should be few and far between.
|
|
|
|
|
|
|
|
| |
Not entirely happy with this. Maybe we'll find a better name. But at
least it's an improvement.
One part I *am* happy with is renaming string-replace to replace,
string-append to append, etc. Overdue, now that we have static dispatch.
|
| |
|
| |
|
|
|
|
|
| |
We still can't have decent tests in this variant.
Thanks Jack and Caleb Couch.
|
|
|
|
| |
Now we can collect all traces, just modulating the depth.
|
|
|
|
|
|
| |
With our new type checks it's no longer possible to expand traces
generated directly in the sandbox. So now there's yet another test that
we can't run in the sandbox/ app. Yet.
|
| |
|
| |
|
|
Thanks Jack and Caleb Couch for the idea.
|