release-capricon-0.13.1.2

Correct the De Bruijn indices when inferring (and printing) the types…

release-capricon-0.13.1.1

Correct the 'substitute' and 'intro before' builtins

release-capricon-0.13.1

Implement a new kind of "quiet" mustache in CaPriCon, to allow precis…

release-capricon-0.13

Upend the CaPriCon rendering pipeline, to allow for multiple output b…

release-capricon-0.12.3

Correct the behavior `type_of` function, causing it to fail on ill-ty…

release-capricon-0.12.2.1

Make CaPriCon preserve whitespace at the end of documents

release-capricon-0.12.2

Release CaPriCon 0.12.2, to make the new stylesheets useable in WiQEEs

release-capricon-0.12.1

Make the order of evaluation left-to-right at all backquote depths in…

release-capricon-0.12: Make better backquotes for CaPriCon

The old "{@ ... @}" syntax was a bit clunky, so I looked for a way to
make it more like the Lisp backquotes. That meant re-using the '}'
keyword for closing both quotes, and unquotes.

Since that meant introducing additional state into the interpreter, I
took it as an opportunity to put that information to good use, and
actually start discriminating between "constant" quotes and "exec"
quotes. Indeed, the ",{ ... } exec" pattern seemed to be common enough
that it deserved its own concept. Enter "${ ... }", and the notion of
"exec step".

This new distinction will also allow some rudimentary levels of
"compilation" to be offered to the users, by means of a function that
turns every "verb step" into the "exec step" that corresponds to that
verb's value at the time of linking. It's quite simple, but if it
could eliminate verb lookups from commonly-used functions, it could be
a nice easy performance win.

release-curly-0.59.5

Update the CI scripts to handle packaging cached builds