capnproto-rust
capnproto-rust copied to clipboard
capnproto
Cap'n Proto for Rust
The current getting started text from https://crates.io/crates/capnp-rpc would benefit from additional clarity in the following section... ``` and you can include the generated code in your project like this: pub...
From the documentation, it's unclear if Builders can be re-used. The presence of ```init_root()``` gives the impression that a Builder can be re-initialized for construction of a new message. Given...
Some pseudocode ``` rust let mut address_book = try!(message_reader.get_root::()); let mut people = address_book.get_people()[0]; // Fixed width data, not Cow people.id = 333; // Dynamic width data, Cow people.email =...
capnproto-c++ has [`thisCap`](https://github.com/capnproto/capnproto/blob/44f5f5686962f3c8ff95618785d1998efd63a779/c%2B%2B/src/capnp/capability.h#L335). I imagine we could achieve something similar by adding a `get_self() -> Client` method to [`ParamsHook`](https://github.com/capnproto/capnproto-rust/blob/dd67e97405bcd23082f221f7a1a2d6b57de1e47d/capnp/src/private/capability.rs#L102) and [`Params`](https://github.com/capnproto/capnproto-rust/blob/dd67e97405bcd23082f221f7a1a2d6b57de1e47d/capnp/src/capability.rs#L155).
I admit defeat :) Continuing this question from IRC...I've been unable piece together how to appropriately use Owned. I'm not familiar enough with capnp or Rust lifetimes to work out...
`capnproto-rust` is currently impenetrable besides the examples. If one is not already familiar with using it in C++, it's very hard to "dive in".
As I see capnproto is all about non copy/ in-place casting so If at any point you need to deep copy all effort is lost. https://github.com/nikomatsakis/rayon is a parallel crate...
As I could see there is no way to set elements using a mutable iterator.
[The crates documentation discusses build scripts](http://doc.crates.io/build-script.html) where you would have a git submodule in tree which is built. Usually this is done in a separate `-sys` crate but there's no...
