04:25 <bfrog> I'm a bit confused by the capnp-rpc generated code and how to use it with rust, I'm wondering given that the types are known why the function calls look like fn call(&mut self, req: CallParams, mut res: CallResults) -> Promise<(), Error>

04:27 <bfrog> I'm mostly wondering why it wouldn't just look more like the interface I define in the capnp file

17:06 <dwrensha> bfrog: the Params and Results structs allow the RPC system to avoid copying the data

17:07 <dwrensha> the data you read from Params still lives in the buffer that it was originally read into from the wire

17:07 <dwrensha> and the data you write into Results gets directly put into the buffer that will eventually get written to the wire

17:08 <dwrensha> in theory we could also provide a more Rust-native interface

17:09 <dwrensha> just like in theory we could generate Rust-native structs for each struct defined in a capnp file

18:17 <BlueNinja> mornin