| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Fix CI.
|
| |
|
|
|
|
|
| |
Move my todos over the past couple of years into the codebase now that
it might be going dormant.
Surprising how few todos left undone!
|
| |
|
|
| |
Couple of fixes to example programs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Periodic cleanup to replace 'reply' with 'return' everywhere in the
repo.
I use 'reply' for students to help reinforce the metaphor of function
calls as being like messages through a pipe. But that causes 'reply' to
get into my muscle memory when writing Mu code for myself, and I worry
that that makes Mu seem unnecessarily alien to anybody reading on
Github.
Perhaps I should just give it up? I'll try using 'return' with my next
student.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Stop requiring jump instructions to explicitly provide a ':label' type
for jump targets.
This has been a source of repeated confusion for my students:
a) They'd add the ':label' to the label definition rather than the
jump target (label use)
b) They'd spend time thinking about whether the initial '+' prefix was
part of the label name.
In the process I cleaned up a couple of things:
- the space of names is more cleanly partitioned into labels and
non-labels (clarifying that '_' and '-' are non-label prefixes)
- you can't use label names as regular variables anymore
- you can infer the type of a label just from its name
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Undo commit 3340. Let's standardize names of non-core files to only have
dashes. That's also consistent with the edit/ and sandbox/ apps. Mu
programmers will tend to pervasively use dashes, just like Lisp
programmers.
Scripts will continue to use underscores..
|
| |
|
|
|
|
|
|
| |
Rename files to be consistent with my (forgotten) convention of always
using underscores over hyphens.
I'll leave server-socket.mu alone for now, since Stephen's hacking on
it.
|
| |
|
|
| |
Process type abbreviations in container definitions.
|
| |
|
|
|
| |
In the process I've uncover a couple of situations we don't support type
abbreviations yet. They're next.
|
| |
|
|
|
|
|
|
| |
I'm going to focus on two projects for a while:
a) the testable interface for file system and network
b) a compiler translating some language to x86
b) might require first gaining some experience programming in Assembly.
|
| |
|
|
| |
Make 'stream' generic.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Fix a bug in phase ordering discovered while trying to stash cells in
the lambda compiler.
|
| |
|
|
|
| |
Manual tests for parse errors because scenarios can't handle assertion
failures yet.
|
| | |
|
| | |
|
| |
|
|
| |
Parsing pairs of atoms.
|
| | |
|
| |
|
|
|
| |
Reorganize parser to make room for parsing pairs. But first test for
pairs is still failing.
|
| |
|
|
| |
Handle multi-character atoms.
|
| |
|
|
| |
Degenerate 'parser' that handles just atoms of one character.
|
| | |
|
| | |
|
| |
|
|
|
| |
Reorganize data structure for lambda cells. Create our first real unit
test for the compiler in the process.
|
|
|
Nothing runs yet. Just spewing out code at this point, as a kind of
sketching.
|