capnproto-rust

What do you mean by "standard Rust data structures"? Like protobuf and other such formats, capnp uses code generation. The tooling for Rust is at https://github.com/capnproto/capnproto-rust and the generated code gives you structs that wrap borrowed data and give you accessors rather than direct field access.

Hi, I have some questions about Sanakirja, if you don't mind.. It stores 4kb blobs, right? Does Pijul first parse the data (copying it to other allocations), or does it use the data as is? I mean, there are some libraries like cap'n'proto[0] and rkyv[1] that can directly use the file contents as an in-memory data structure, without a deserialization step (or rather, deserialization is simply a quick validation to check the data isn't corrupted), I was wondering if Pijul did anything like that. And like, is this btree header [2] stored exactly like this on disk, and does Sanakirja exploits this to avoid further copying data? (I guess there's a trouble with compression there: to decompress you really need to write in another buffer) Also, is the I/O done with something that prevent userspace copies like mmap or io_uring, or does it eventual

Impressive work! I just wish it had a less awkward API for serialisation and deserialisation. Compare the Rust example for Capnp with Protobuf: https://github.com/capnproto/capnproto-rust/blob/master/exam... https://docs.rs/prost/0.6.1/prost/trait.Message.html#method.... (Ok I couldn't actually find an example for Prost because all you do is create a normal Rust `struct` and call `encode()` on it.)

Cap'n Proto has a high-quality Rust implementation: https://github.com/dwrensha/capnproto-rust

There's also capnproto-rust[1] if anyone was wondering. [1]: https://github.com/dwrensha/capnproto-rust

Rust does have unsafe direct memory access and a work-in-progress port of Cap'n Proto (https://github.com/dwrensha/capnproto-rust).

Author here. The makefiles I'm using are on github: https://github.com/dwrensha/capnproto-rust/blob/master/Makef... https://github.com/dwrensha/capnproto/blob/benchmark/c%2B%2B... I compiled libcapnp with the latest Clang g++ that ships with XCode. It perhaps would be more fair to also compile the C++ benchmarks with Clang, instead of the Macports gcc4.8 that I'm using, but unfortunately Clang barfs on some template hackery in the benchmark driver.