Ivan FB 0e176bd5eb
fix(ffi): set up foreign-thread GC in entry procs; recycle/event cleanup
- 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>
2026-06-12 11:28:48 +02:00
..
2026-06-01 13:34:56 -03:00
2026-06-01 13:34:56 -03:00
2026-05-19 12:43:34 +02:00

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 the MyTimerCtx API
  • src/api.rs: High-level async/sync wrapper around the FFI
  • src/ffi.rs: Raw extern "C" declarations for the Nim library
  • src/types.rs: Serializable Rust types matching the Nim FFI types
  • build.rs: Build script that compiles the Nim library to libmy_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:

  1. Invokes the Nim compiler with -d:targetLang:rust flag
  2. Triggers genBindings("examples/timer/rust_bindings", "../timer.nim") in timer.nim
  3. 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.