Files
zeekay 1ae8d33fa5 ci: fix minrust (pin quickcheck =1.0.3) + formatting (nightly cargo fmt)
Two pre-existing CI failures (unrelated to codegen/install-zap):
- minrust 1.81: quickcheck 1.1.0 pulls rand 0.10 -> rand_core 0.10.1, whose
  Cargo.toml requires the edition2024 feature (unstable on Cargo 1.81). Pin
  quickcheck to =1.0.3 (last version on rand 0.8 / rand_core 0.6.4) — within
  MSRV, no major bump. Fresh-resolve verified: rand_core 0.10.1 leaves the graph.
- formatting: ran 'cargo +nightly fmt --all'; the CI check
  (--check --unstable-features --error-on-unformatted, nightly) now passes.
2026-06-20 02:13:18 -07:00
..
2018-01-15 16:09:50 -05:00

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