Ivan FB 914c70a131
fix(codegen): C++ bindings target the *_cbor exports
The C++ wrapper speaks CBOR, but after the native/CBOR split it still called the
bare `<name>` symbols — which are now the *native* (typed-args) entry points, so
every C++ call hit the wrong ABI and the C++ e2e failed 19/19 (also reddening
the ASan/TSan jobs, which run the same suite). Point the generated extern
declarations and call sites at `<name>_cbor` for `{.ffi.}` procs and the ctor;
the destructor has no CBOR variant and stays bare. Regenerated the timer and
echo C++ bindings. C++ e2e back to 19/19.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-31 16:31:12 +02:00
..
2026-05-28 22:40:33 +02:00
2026-05-19 12:43:34 +02:00

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 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/timer
nimble genbindings_cpp

This command:

  1. Invokes the Nim compiler with -d:targetLang:cpp flag
  2. Triggers genBindings("examples/timer/cpp_bindings", "../timer.nim") in timer.nim
  3. 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.