mirror of
https://github.com/logos-messaging/nim-ffi.git
synced 2026-06-21 00:40:16 +00:00
- Call initializeLibrary() (setupForeignThreadGc) in the `.ffi.` request wrapper and in add/remove_event_listener so a foreign (Go) caller thread has an initialised Nim heap before any allocation ($reqTypeName / $eventName / registry ops). Without it such a thread segfaults in the allocator under GC pressure — the production unwrap SIGSEGV. - recycleContext resets the event registry/queue + stuck flag on park so a reused pool slot starts clean. - ffiDtor doc/cleanup for the async recycle ABI. 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.