3193

Bugfix: 'restart' should never restart completed routines. They will
often have nothing to run.

I ran into this while considering whether 'read' on channels to return
true on success or failure. Switching from 'fail?' to 'success?'
crashed. But now that it's fixed I think I'll keep things the way they
are. No reason to be consistent with 'next-ingredient' and have the
status be true to signal success.

0 files changed, 0 insertions, 0 deletions