nim-ffi

mirror of https://github.com/logos-messaging/nim-ffi.git synced 2026-05-17 07:39:34 +00:00

History

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

codegen

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

2026-05-11 21:44:53 +02:00

internal

better onDestroy sync

2026-05-10 11:38:43 +02:00

alloc.nim

Fix memleaks (#11 )

2026-04-27 21:22:45 +02:00

ffi_context.nim

better onDestroy sync