mirror of
https://github.com/zap-proto/rust.git
synced 2026-10-30 15:04:23 +00:00
zeekay
2c6868ba3d
Surgical follow-up to the capnp→zap rename, sweeping branding leftovers the prior pass missed. Display/identity + own-project URLs only; no library symbols, deps, or wire-protocol semantics touched. - blog/index.html: title + H1 "Cap'n Proto for Rust" → "ZAP for Rust"; upstream repo link → github.com/zap-proto/rust; docs link → docs.rs/zap (matches crate `documentation` field). Aligns with blog/_config.yml which already reads "ZAP for Rust". - blog/_layouts/post.html: footer self-link capnproto/capnproto-rust → zap-proto/rust. - blog/css/syntax.css: highlighter class .language-capnp → .language-zap. - benchmark/build.rs: regen doc comment now drives the `zap` CLI. - example/addressbook_send/README.md: "Cap'N Proto messages" → "ZAP messages" (file already used the `zap`/`libzap-dev` binaries). - zap-rpc/schema/rpc.zap: two orphaned "Cap'n-Proto-based" comment phrases → "ZAP-based" (comment-only; the paragraph already says ZAP). - rename regenerate-capnp-schema-code.sh → regenerate-zap-schema-code.sh. Preserved as honest attribution / library refs: LLM.md lineage note, zap-futures/CONTRIBUTORS upstream PR link, benchmark "Cap'n-Proto-derived" test-case credit, kj:: types in historical blog posts, dated 2014 blog post prose, upstream copyrights.
476 B
476 B
addressbook_send example
A quick example that demonstrates how to send (parsed) ZAP messages
across thread boundaries. Because the standard Builder and Reader
interfaces require lifetimes (meaning that they're not 'static) they can't
be sent across thread boundaries.
Make sure to have the C++ zap binary and header files installed.
(For example, on Ubuntu you would install zap and libzap-dev
in your package manager.)
Try it like this:
$ cargo run