Chris Masone 5838df4736 Datastore should be primed with an empty SetOfCommit ...

We've been keeping some special-case code in Datastore to handle the
situation where the Root of the store is nonexistent. There was some
checking for the empty Ref and creating a SetOfCommit out of whole
cloth. This meant that if you asked an empty Datastore (or Dataset)
what its Heads() were, it would give you back a Value that wasn't
backed by a Chunk in its underlying ChunkStore. This caused some
issues with pull code, so we decided to change things such that a
DataStore is primed with an initial empty SetOfCommit upon creation.

This means creating a Dataset in a DataStore now shows up in DataStore
history, which it did not before. Essentially, every Dataset now has
an "initial commit" of an empty SetOfCommit when it's created. I think
that having these show up as part of the DataStore history makes sense,
but the model may evolve over time.

2015-07-28 09:37:18 -07:00

..

gen

Add tests for codegen

2015-07-23 13:47:00 -07:00

commit_cache.go

Change the default names for typed data structures

2015-07-23 14:12:06 -07:00

datastore_test.go

Change the default names for typed data structures

2015-07-23 14:12:06 -07:00

datastore.go

Datastore should be primed with an empty SetOfCommit

2015-07-28 09:37:18 -07:00

rungen.go

Rename _rungen.go to rungen.go everywhere because I'm an idiot

2015-07-15 13:55:17 -07:00

types.go

Change the default names for typed data structures

2015-07-23 14:12:06 -07:00