Ivan FB 7764b2f43b
fix C++ "async" methods spawn a thread per call that then blocks on a condvar (cpp.nim:362–377). std::async(std::launch::async, ...) forces a fresh thread, and the body runs
the blocking ffi_call_ which waits on a condvar with the user's timeout (default 30s). Under load this is a thread-explosion factory, and the name "async" is misleading — the
  Rust side has real async via tokio oneshot, but the C++ side has fake async. If true async isn't reachable in C++ without coroutines, fine, but at least pool the threads or
  document this is just a convenience wrapper.
2026-05-11 21:44:53 +02:00
..
2026-05-10 11:38:42 +02:00
2026-05-10 11:38:41 +02:00

C++ Bindings for nim-timer

Purpose

This folder contains auto-generated C++ bindings for the nim_timer Nim library. It is generated from ../nim_timer.nim and provides:

  • nimtimer.hpp: High-level C++ class (NimTimerCtx) wrapping the FFI interface
  • main.cpp: Example executable demonstrating how to use the bindings
  • CMakeLists.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/nim_timer
nimble genbindings_cpp

This command:

  1. Invokes the Nim compiler with -d:targetLang:cpp flag
  2. Triggers genBindings("examples/nim_timer/cpp_bindings", "../nim_timer.nim") in nim_timer.nim
  3. Creates/updates the generated binding files

Building the Example

cd examples/nim_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.