| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
I'm dropping all mention of 'recipe' terminology from the Readme. That
way I hope to avoid further bike-shedding discussions while I very
slowly decide on the right terminology with my students.
I could be smarter in my error messages and use 'recipe' when code uses
it and 'function' otherwise. But what about other words like ingredient?
It would all add complexity that I'm not yet sure is worthwhile. But I
do want separate experiences for veteran programmers reading about Mu on
github and for people learning programming using Mu.
|
| |
|
|
| |
First step to reducing typing burden. Next step: inferring types.
|
| |
|
|
| |
..now that we support non-integers.
|
| | |
|
| |
|
|
| |
I've tried to update the Readme, but there are at least a couple of issues.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Bring back the example program.
|
| |
|
|
|
|
|
|
|
| |
They need a type table to work, but I'm keeping type tables next to
the tests.
Everything needs to be a test from now on.
(But first some fixes to the terminal primitives.)
|
| | |
|
| |
|
|
|
|
|
| |
As expected, mu works just as well with named variables.
Maybe I want to insert the local stack frame computations automatically
using the assembler? How to indicate globals then? Add 'local' metadata only
if 'global' is absent? What about lexical stack frames?
|
| |
|
|
| |
Broken since commit 11 on Jul 10.
|
| | |
|
| | |
|
| |
|