about summary refs log tree commit diff stats
path: root/tangle.mu
Commit message (Collapse)AuthorAgeFilesLines
* 428 - cleanup odds and endsKartik K. Agaram2014-12-141-13/+13
|
* 403 - 'function' is more clear than 'def'Kartik K. Agaram2014-12-121-2/+2
|
* 401 - stop abbreviating opsKartik K. Agaram2014-12-121-4/+4
| | | | | We expect users to come across mu from arbitrary bits of code, so try to make each line as self-contained as possible.
* 321 - before/after can now come anywhereKartik K. Agaram2014-11-241-24/+9
| | | | | | This pollutes our traces with all 'system software'. Too much trouble to keep it out; just lump it for now. Who knows, might even be useful. Most of the time convert* labels are easy to grep out when debugging.
* 319 - ack, forgot to handle blocks when tanglingKartik K. Agaram2014-11-241-0/+50
Will the 'lightweight tools' really be all that useable if we encourage people to layer them one atop another and track precisely what inputs each can accept? Something to keep an eye on. In the meanwhile, we have a new (but very unrealistic) example demonstrating the tangling directives. There's still a big constraint on ordering: before/after clauses have to come before functions that need them.