mirror of
https://github.com/logos-messaging/nim-ffi.git
synced 2026-06-21 08:49:34 +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>
C++ Bindings for nim-timer
Purpose
This folder contains auto-generated C++ bindings for the my_timer Nim library. It is generated from ../timer.nim and provides:
my_timer.hpp: High-level C++ class (MyTimerCtx) wrapping the FFI interfacemain.cpp: Example executable demonstrating how to use the bindingsCMakeLists.txt: Build configuration that compiles the Nim library and links the C++ example
How It's Generated
Generate or regenerate these bindings by running from the parent directory:
cd examples/timer
nimble genbindings_cpp
This command:
- Invokes the Nim compiler with
-d:targetLang:cppflag - Triggers
genBindings("examples/timer/cpp_bindings", "../timer.nim")intimer.nim - Creates/updates the generated binding files
Building the Example
cd examples/timer/cpp_bindings
cmake -S . -B build
cmake --build build
./build/example
Do Not Edit
The generated files in this folder are overwritten each time nimble genbindings_cpp runs. Any manual changes will be lost.