anchor.diff:  statement and it is out of date, Ninja will rebuild and reload it
   before building the targets requested by the user.
   
  +More details
  +------------
   
   The `phony` rule
   ~~~~~~~~~~~~~~~~
  
positive.code: from then on `$name` expands to the static string as the result of the
  expansion.  It is never the case that you'll need to "double-escape" a
  value to prevent it from getting expanded twice.
  
  
  Future work
  -----------
  
  Some pieces I'd like to add:
  
  _inotify_.  I had originally intended to make Ninja be memory-resident
  and to use `inotify` to keep the build state hot at all times.  But
  upon writing the code I found it was fast enough to run from scratch
  each time.  Perhaps a slower computer would still benefit from
  inotify; the data structures are set up such that using inotify
  shouldn't be hard.
  
  _build estimation and analysis_.  As part of build correctness, Ninja
  keeps a log of the time spent on each build statement.  This log
  format could be adjusted to instead store timing information across
  multiple runs.  From that, the total time necessary to build could be
  estimated, allowing Ninja to print status like "3 minutes until
  complete" when building.  Additionally, a tool could output which
  commands are the slowest or which directories take the most time
  to build.
  
negative.code: depfile='$out.d')` and it will generate the appropriate syntax.  Feel
  free to just inline it into your project's build system if it's
  useful.
  
  Extra tools
  -----------
  