c39f91172da2

Update
[view raw] [browse files]
author Steve Losh <steve@stevelosh.com>
date Sat, 02 Jul 2016 22:38:28 +0000
parents 6f99041a367f
children 2d0544a80fdd
branches/tags (none)
files README.markdown

Changes

--- 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.