David Renshaw

> My first thought would be to generate rust struct definitions for each capn proto struct. Since all built-in types seem to have direct Rust equivalents, this should always be...

I agree that such support for parallel processing sounds useful! I don't think I'll have time in the near future to investigate exactly what would be involved; if you look...

It's possible to turn your `Proxy` object into a `Client` and then call it directly, without needing to construct any `RpcSystem`. There are some examples of this in the test...

I think the important thing to remember is: a `Server` is something you implement, and a `Client` is something you call. The main documentation we have for this stuff right...

Related: #549, which was reverted in #578.

Yep, the `init_` methods clear out the old data, but don't reclaim the old space. More documentation about this would be good.

You can reuse a `message::Builder`, but the usefulness of doing so is limited because you will continue to accumulate unused memory that can only be reclaimed by dropping the `message::Builder`....

It would definitely be good for capnproto-rust to support orphans! I think the API will need to be somewhat different from the corresponding C++ API in order to satisfy the...

Interesting suggestion! I guess we could basically follow the pattern of [libgit2-sys](https://crates.io/crates/libgit2-sys) and add a submodule pointing to the [capnp compiler source code](https://github.com/sandstorm-io/capnproto). I think it would make sense to...

You'll need to install Cap'n Proto from git: https://github.com/kentonv/capnproto. The 0.5 release is coming soon. You're right that I should probably add some documentation about this.