capnproto-rust
capnproto-rust copied to clipboard
capnproto
Cap'n Proto for Rust
The Rust team yesterday accepted [this RFC on a standard Allocator interface](https://github.com/rust-lang/rfcs/pull/1398). It hasn't been implemented yet, but I was taking a look and it seems like it would cover...
The c++ api has [orphan support](https://capnproto.org/cxx.html#orphans) are there plans to adding it to the rust api? It seems like the only way to do a bottom-up building of a capn'proto...
Generated code produces a large amount of non_camel_case_types and dead_code warnings, it should be marked `allow` so that `rustc` doesn't complain.
Especially with cargo, generating code using tools can be annoying. Add a syntax extension that will generate the code into a module. With `include_str` etc, no flexibility is lost.
In some sense it acts as a `get_unchecked` method but is not exposed publicly anymore to prevent rogue implementations.
* Renames `ReadSegmentTableResult` to `NoAllocSegmentTableInfo` and makes it public. * Renames `NoAllocBufferSegments::from_segment_table()` to `NoAllocBufferSegments::from_segment_table_info()` and makes it public.
It would be advantageous to enable the creation of NoAllocSliceSegments along with a buffer and NoAllocBufferSegmentType, particularly when the message has already undergone parsing. While this capability was present until...
See https://github.com/capnproto/capnproto-rust/issues/230#issuecomment-1690113298. The `capnp-rpc` does not yet natively support streaming methods. Methods that use the `streaming` keyword are supposed to fall back to the [`StreamResult` struct](https://github.com/capnproto/capnproto/blob/93da77776dd3fa3d258cc3de49fc0c948ea38019/c%2B%2B/src/capnp/stream.capnp#L30), but there is currently...
Currently, the `Allocator` of a `message::Builder` functions as an API for some kind of Malloc/Free. This is fine when the message to be encoded resides in host memory that we...
