mirror of
https://github.com/logos-messaging/nim-ffi.git
synced 2026-06-20 16:29:31 +00:00
The Rust wrapper speaks CBOR, but after the native/CBOR split it still declared and called the bare `<name>` request symbols — which are now the *native* (typed-args) entry points, so every Rust request hit the wrong ABI (struct/ptr mismatch). This is the Rust counterpart of the C++ fix (914c70a), which was missed at the time. Point the ffi.rs externs and the api.rs ctor/method calls at `<name>_cbor`; the destructor has no CBOR variant and the event registration is unchanged here. Verified at runtime: the rust_client now creates a context and round-trips version / echo / schedule over CBOR. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Rust Bindings for nim-timer
Purpose
This folder contains auto-generated Rust bindings (the my_timer crate) for the my_timer Nim library. It is generated from ../timer.nim and provides:
src/lib.rs: Main library exposing high-level Rust types and theMyTimerCtxAPIsrc/api.rs: High-level async/sync wrapper around the FFIsrc/ffi.rs: Rawextern "C"declarations for the Nim librarysrc/types.rs: Serializable Rust types matching the Nim FFI typesbuild.rs: Build script that compiles the Nim library tolibmy_timer.dylib(or.so/.dll)Cargo.toml: Package manifest with serde and serde_json dependencies
How It's Generated
Generate or regenerate these bindings by running from the parent directory:
cd examples/timer
nimble genbindings_rust
This command:
- Invokes the Nim compiler with
-d:targetLang:rustflag - Triggers
genBindings("examples/timer/rust_bindings", "../timer.nim")intimer.nim - Creates/updates the generated binding files
Using as a Dependency
The rust_client example consumes this crate:
[dependencies]
my_timer = { path = "../rust_bindings" }
Do Not Edit
The generated files in this folder are overwritten each time nimble genbindings_rust runs. Any manual changes will be lost.