| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We'll make 'buffer' properly generic at some point. Basically need to
support multi-word types.
x:list:integer <- copy y:list:integer # ok
x:list <- copy y:list:integer # ok
x:list:integer <- copy y:list # error
We'll need a separate runtime operator like maybe-coerce for the third
case.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the right time for this change I've been meaning to make,
because it lets me drop my hack in 'abort-to'.
'abort-to' is likely still a bad idea because:
a) Just because this example doesn't need to clear a few things on
abort doesn't mean such use cases don't exist. In other words, there's
no way to tell if your stack frame recently returned from an abort.
That question isn't even well-posed at the moment; what does
'recently' even mean?
b) I may need to run deferred statements on each stack frame, and it's
not clear how to rewrite 'defer' to be robust to aborts. Exceptions
entering through the back door?
Looks like all this is expected when implementing exception-like
behavior using continuations:
http://matt.might.net/articles/implementing-exceptions
c) Of course we don't have composable exceptions. I still don't grok
the value of that. We don't need yield since we have channels. What
else might we need continuations for? Let's try to come up with a
clean way to implement the amb operator or something.
http://www.randomhacks.net/2005/10/11/amb-operator
|
| |
|
|
|
|
|
| |
Poor man's continuation. Not first class or delimited yet. And we see
the problem: hard to specify precisely what to do after unwinding the
stack. We start reaching for a try/catch statement. But let's see if
there's a better way.
|
| |
|
|
| |
Yet another 'grow-buffer' bug.
|
| |
|
|
| |
'grow-buffer' was never working until now. Too much spiking lately.
|
| |
|
|
| |
'#\\' only contains one escape character: the first backslash
|
| |
|
|
|
|
|
|
| |
Ran into this in color-repl.mu: I wasn't checking struct variables in
'get' operations.
Still no way to test for use-before-set logic. But we'll fix it when we
leave arc behind.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backspace kinda works. Parens are colored in three rotating colors which
helps with balancing. Comments and strings are colored.
But it's hard to handle backspace in all situations. Like if you
backspace over a quote you have to either quit the string-slurping
routine you're in, or return to string slurping mode. Similarly for
comments; *there* you don't even have a end delimiter to let you know
you're back in a comment. You have to keep track of what came before.
I experimented with a library but it interacts poorly with the charterm
library I'm already using. Ended up with a gross inefficient approach
instead.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
(Another attempt at 623.)
I dunno, this may all be a wild goose chase. I haven't been disciplined
in tagging in-out arguments in 'read-move' and its helpers. Maybe I
should just drop those 'nochange' oargs in 'read' and 'write'. Maybe I
should reserve output args only for return values that callers might
actually care about, and use more conventional metadata like 'const' or
'unique' or 'inout' on other args.
|
| |
|
|
|
|
|
|
|
| |
I dunno, this may all be a wild goose chase. I haven't been disciplined
in tagging in-out arguments in 'read-move' and its helpers. Maybe I
should just drop those 'nochange' oargs in 'read' and 'write'. Maybe I
should reserve output args only for return values that callers might
actually care about, and use more conventional metadata like 'const' or
'unique' or 'inout' on other args.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
I just did this in 611; what's the point of all this if tests can't stay
passing?
I don't understand why buffered-stdin.mu needs to preempt itself. stdin
and buffered-stdin somehow end up sharing a single circular buffer,
that's probably causing a race condition.
|
| |
|
|
|
|
| |
2 bugs found:
a) Have to slurp the newlines.
b) Have to clear the line-buffer at the start of each line.
|
| |
|
|
| |
Chessboard now *almost* handles backspace perfectly.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Shove the complexity of reading newlines as low as possible.
|
| | |
|
| |
|
|
|
|
| |
Shove the complexity of printing newlines as low as possible.
Definite instability in that one trace.
|
| |
|
|
|
|
|
|
|
|
| |
We need the hack of printing characters typed to screen right after we
see them. But only when it's the real screen. And there's no way to
write a test for that because it explicitly shouldn't happen for fake
terminals :(
Never mind, we'll be able to test it when we provide some mechanism for
suppressing print. The equivalent of 'stty -echo'.
|
| |
|
|
|
| |
Still surprisingly hard to debug. We might be barking up the wrong tree.
Or we might just need to lump it. System software is hard.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Use asynchronous channels like 'stdin' for most tests.
Use the synchronous fakes for testing low-level stdin helpers.
|
| | |
|
| | |
|
| |
|
|
| |
Also cleaned up much of the mess in 594.
|
| |
|
|
|
|
| |
I'd caused a bug in Arc: https://github.com/arclanguage/anarki/commit/97b3464256
Almost done interrupting and restarting routines.
|
| |
|
|
|
| |
Now that there isn't a stdout channel we can postpone the test showing
the need to flush-stdout before clearing screen.
|
| | |
|
| | |
|
| |
|
|
|
| |
Also clean up various prints from last few commits.
As a convention, for debugging we always print directly to host.
|
| |
|
|
|
|
|
|
| |
I discovered the problem when playing more than 3 moves in the
chessboard app.
But it turns out we've been clobbering each other willy-nilly even in
the chessboard-retro app.
|