Ivan FB 918dd72390
feat(ffi): native event delivery + dual-ABI event symbol naming
Events now mirror the native/CBOR split already in place for requests, with the
same symbol-naming convention:

- `<lib>_add_event_listener`      -> NATIVE listener (typed `<T>Pod` by pointer)
- `<lib>_add_event_listener_cbor` -> CBOR listener (EventEnvelope bytes)

Framework: `FFIEventListener` gains a `native` flag; `addEventListener` a
`native` param; a new `dispatchFFIEventDual` template builds the `<T>Pod` once
for native listeners (`nimToPod`/`freePod`) and the CBOR envelope once for the
rest, fanning each out — so a single `{.ffiEvent.}` dispatch serves both kinds.
`declareLibrary` exports both registration entry points.

Generators: the bare `<lib>_add_event_listener` is the native symbol; every
CBOR consumer (C/C++/Go/Rust) now targets `<lib>_add_event_listener_cbor`. The
rename and the generator updates ship together so the bare name is never briefly
broken. Bindings regenerated.

Validated: native-event unit test (typed POD to native + CBOR to cbor listener,
orc/refc/ASAN); full unit suite; C++ e2e 19/19; Go example; existing event
tests unchanged. The per-event *typed* native callback + wildcard router (the
ergonomic consumer surface) is a follow-up.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-31 18:37:27 +02:00
..
2026-05-19 12:43:34 +02:00
2026-05-19 12:43:34 +02: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.