| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
More verbose, but it saves trouble when debugging; there's never
something you thought should be traced but just never came out the other
end.
Also got rid of fatal errors entirely. Everything's a warning now, and
code after a warning isn't guaranteed to run.
|
| |
|
|
|
|
|
| |
It comes up pretty early in the codebase, but hopefully won't come up
in the mu level until we get to higher-order recipes. Potentially
intimidating name, but such prime real estate with no confusing
overloadings in other projects!
|
| |
|
|
|
| |
Requires better support for special variable names in scenarios like
'screen' and 'console'.
|
| |
|
|
|
|
|
|
| |
This takes away the need for multi-level escaping in scenario setup.
Post-conditions like screen-should-contain are still an issue, though.
Maybe each string literal should be able to specify escapes inside its
syntax? Or at a per-instruction granularity?
|
| | |
|
| |
|
|
|
|
| |
First, undo our existing hacky pseudo-support.
Some repl tests currently breaking.
|
| | |
|
| |
|
|
|
|
|
|
| |
repl.mu now passing again. But still I have concerns:
a) Doubling backslashes in tests. Hard to tell how many levels to add.
b) I think the read-key interface needs to go. But then how do we handle
send-keys-to-channel and other flows like that in the chessboard app?
|
|
|
Only core layers currently passing. Console apps are probably still
broken.
|