Why?

[rcrowley]

(Not a bug but I thought this would be the most discoverable place for others to find the answer.)

Was there any deficiency in http://code.google.com/p/leveldb-go/ that led you to build this cgo implementation?

[milaz]

Please note the difference: leveldb-go is a re-implementation of LevelDB in Go language, while levigo is Go binding to LevelDB library. You might want to see this discussion for clarification:
https://groups.google.com/d/topic/golang-nuts/YKHDSKfCaq0/discussion

As far as I understand, at the time when work on levigo started, leveldb-go was not completely implemented. (Is it complete yet?)

[rcrowley]

I knew leveldb-go was a reimplementation but was curious why. Up-to-dateness is a perfectly valid reason to use this wrapper. Thanks for the lin, @milaz.

[jmhodges]

Yep, @milaz has got it. I'd love for levigo to be obsoleted by leveldb-go, but that hasn't been the case, yet.