| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2312 | Kartik K. Agaram | 2015-10-29 | 1 | -1/+1 |
| | | |||||
| * | 2310 - add some more tracing | Kartik K. Agaram | 2015-10-29 | 1 | -0/+4 |
| | | | | | | | | | | | | I've been growing lax on white-box testing when it's one of the three big thrusts of this whole effort. Perhaps it was because I got too obsessed with keeping traces stable and didn't notice that stable doesn't mean "not changing". Or perhaps it's because I still don't have a zoomable trace browser that can parse traces from disk. Or perhaps $trace-browser is too clunky and discourages me from using it. Regardless, I need to make the trace useable again before I work much more on the next few rewriting transforms. | ||||
| * | 2308 - auto-reply on fall-through | Kartik K. Agaram | 2015-10-28 | 1 | -0/+30 |
| | | |||||
| * | 2306 - recipe headers | Kartik K. Agaram | 2015-10-28 | 1 | -0/+111 |
| Once a student has gotten used to recipes and ingredients using the staged 'next-ingredient' approach there's no reason to avoid conventional function headers. As an added bonus we can now: a) check that all 'reply' instructions in a recipe are consistent b) deduce what to reply without needing to say so everytime c) start thinking about type parameters for recipes (generic functions!) | |||||