The API is still very basic and suffering from multiple Nim issues
that will be resolved in the near future:
* destructors will handle the resource cleanup better
* converter concepts will enable a wider range of possible types
to be used as keys and values.
The API currently uses an ErrorResult type to communicate errors,
but RocksDB doesn't seem to have many recoverable failure modes
and I anticipate that the API will be migrated to use exceptions
once we get a bit more experience with RocksDB.
The C interface file was moved to a separate directory to make
nimble happy (`nimble check`).
Zahary Karadjov