Great stuff, and I like the use of a sentinel as a terminator symbol.
One aspect of this I would like to explore is that of a lazy sequence as a more
fundamental language primitive. Generators in for loops are great, but
generators returned by lapply() and friends would enable lazy functional
t
Thank you Lionel, Peter, and Duncan!
Some responses inline below:
> Couldn't this all be done in a while or repeat loop? ...
> Not as simple as yours, but I think a little clearer because it's more
> concrete, less abstract.
Indeed, that’s the trade-off! Explicit and verbose vs. simple,
concise,
A followup after some research and discussion with TeXLive people.
This is longstanding behaviour of TeX. When you put a filename on the
command line, it does 3 things:
- If there are quotes on the filename they are stripped off.
- If you are on windows and the filename is a path starting
Clever! If going for non-local returns, probably best for ergonomics to pass in
a closure (see e.g. `callCC()`). If only to avoid accidental jumps while
debugging.
But... do we need more lazy evaluation tricks in the language or fewer? It's
probably more idiomatic to express non-local returns with
