List view

• v0.0.4

  Will introduce a new structure for working with the transformed structures.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• Store state maps

  One of the initial desires for this project is to be able to maintain a sequence of state snapshots in a single logical structure. This could be thought of as somewhat analogous to commits in git, where a commit provides a temporal and evolutionary reference point for a given state tree. Here in `merky`, we're initially just concerned about the temporal or "version" aspect: at "time" or "version" t0, we had state X; at "time"/"version" t1, we had state Y; and so on. When this milestone is complete, we'll have a "state map" structure for providing this functionality.

  Due by June 5, 2015

  •2/2 issues closed
  100% complete0 open2 closed