Relationship between the rocksdb crate or other rust-rocksdb forks? about rust-rocks HOT 9 OPEN

Wraps generic pointers into a c struct, use struct as opaque pointers in Rust. (almost the same as rocksdb c.h API)
Some plain old struct(like Statistics, some callback structs), can be directly mapped as a rust #[repr(C)] struct.

from rust-rocks.

Nice work. I certainly encourage you to keep going on this project. I may switch to using it myself at some point soon, and perhaps contribute, if you need anything!

from rust-rocks.

Thanks. Just published v0.1.0.

from rust-rocks.

Hey @bh1xuw. Is this project abandoned, or have you just not needed to improve its featureset lately?

from rust-rocks.

Yes. Thanks for your pointing out.

• spacejam/rust-rocksdb use pure c.h interface, which lacks some advanced functions. And may introduce some overhead(string conversion, pointer to pointer to the underlying C++ instance.).
• other rust-rocksdb forks, notably pingcap's fork, which has the fullest feature set, never seem to be able to merge to upstream.

This project is for personal experiment & learning.

from rust-rocks.

Will leave this issue forever opened.
(sorry for changing your issue title

from rust-rocks.

Okay, thanks.

I didn't know direct C++ interop was possible. How do you manage that?

from rust-rocks.

@alexreg :) just made it up to date. v0.1.5 published.

from rust-rocks.

@bh1xuw Thanks!

from rust-rocks.