# HG changeset patch # User Steve Losh # Date 1467499108 0 # Node ID c39f91172da257a490e3d067394f98504c8a4978 # Parent 6f99041a367f3f36e38abe29ba811c5865b91928 Update diff -r 6f99041a367f -r c39f91172da2 README.markdown --- a/README.markdown Sat Jul 02 19:08:01 2016 +0000 +++ b/README.markdown Sat Jul 02 22:38:28 2016 +0000 @@ -352,3 +352,12 @@ I think the general rule I'll follow (for now) is to use multiple value returns very sparingly, and only when one of the values is different than the rest and is obviously the "most important" one. +* Worked on [Mazes][] some more. I did a tiny bit more of the [book][Mazes + book] but mostly it was me playing around with [iterate][]. + + Iterate is turning out to be cool. I made some custom drivers for my maze + grids and a couple of custom clauses that are really neat. `(averaging + (...some expr...) :into some-var)` will keep track of the average of the + expression over the life of the loop, and `(timing run-time :since-start-into + v1 :per-iteration-into v2)` sets vars to store timing info. And they even + work together -- in `run-stats` I average the per-iteration times together.