osmaczko 0a6e833b53
feat: implement Client crate and C FFI bindings
Implement a `client` crate that wraps the `libchat` context behind a
simple `ChatClient<D>` API. The delivery strategy is pluggable via a
`DeliveryService` trait, with two implementations provided:

- `InProcessDelivery` — shared `MessageBus` for single-process tests
- `CDelivery` — C function-pointer callback for the FFI layer

Add a `client-ffi` crate that exposes the client as a C API via
`safer-ffi`. A `generate-headers` binary produces the companion C
header.

Include two runnable examples:
- `examples/in-process` — Alice/Bob exchange using in-process delivery
- `examples/c-ffi` — same exchange written entirely in C; smoketested
under valgrind (to catch memory leaks) in CI

iterates: #71
2026-03-30 21:24:29 +02:00

519 B

in-process

An example Rust application built on top of crates/client.

It demonstrates that creating a working chat client in pure Rust is trivial: depend on crates/client, pick a DeliveryService implementation (here the in-memory InProcessDelivery shipped with the crate), and wire up ChatClient. No boilerplate, no FFI.

Running

cargo run -p in-process

The binary performs an Alice-Bob message exchange entirely in-process and prints the exchanged messages to stdout.