mirror of
https://github.com/logos-messaging/nim-ffi.git
synced 2026-06-21 00:40:16 +00:00
The recycle/async-destroy work changed the Nim `ffiDtor` export from `int destroy(ctx)` to `int destroy(ctx, callback, userData)`, but the C++ and Rust generators still emitted the 1-arg signature. Foreign callers therefore passed only `ctx`; inside Nim, `callback`/`userData` held uninitialised register garbage. `requestRecycle` stored the garbage callback and the recycle handler later invoked it — a jump through a wild pointer that segfaulted in every C++ E2E / ASan / TSan job (the crash surfaced at teardown, after each test's assertions had already passed). Generate the 3-arg ABI and have the destructor/Drop block on the recycle callback via the existing sync-call helper, so the pool slot is fully drained and parked before the handle goes away — otherwise rapid create/destroy churn (StressShortLivedPerThreadContext, ThreadedHammer) could outrun the recycle and exhaust the pool. 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.