Files
wickra/bindings/c
kingchenc 0c925aa9d5 feat(c-abi): expose warmup_period / is_ready across the C ABI bindings (#297)
* feat(c-abi): expose warmup_period / is_ready across the C ABI bindings

The C ABI hub exposed new/update/batch/reset/free per indicator but not the
Indicator::warmup_period / is_ready queries that the native (Python/Node/WASM)
bindings already had, so C/C#/Go/Java/R callers could not ask an indicator
whether it was warmed up without feeding it and watching for NaN.

Regenerated from the ScriptHelpers capi + language generators:
- bindings/c: wickra_<ind>_warmup_period (size_t) and wickra_<ind>_is_ready
  (bool) for every indicator (504; the 10 alt-chart bar builders are excluded
  by design). wickra.h regenerated via cbindgen (additive only).
- bindings/csharp: int WarmupPeriod() / bool IsReady() on each wrapper.
- bindings/go: WarmupPeriod() int / IsReady() bool.
- bindings/java: int warmupPeriod() / boolean isReady().
- bindings/r: C glue + registration; hand-written warmup_period() / is_ready()
  S3 generics in methods.R, plus NAMESPACE exports.

Tests: C-ABI Rust unit tests, the C examples/archetypes.c suite, and the C#,
Go, Java and R archetype suites all gain a warmup/is_ready transition check.

* build(go): sync vendored wickra.h with the C ABI header

The Go binding vendors bindings/c/include/wickra.h; refresh it with the new
warmup_period / is_ready declarations so the CI sync check passes.
2026-06-14 01:04:06 +02:00
..

Wickra — C / C++

CI codecov GitHub release License: MIT OR Apache-2.0

Streaming-first technical indicators for C and C++. A prebuilt shared/static library plus a generated wickra.h — no system dependencies.

Wickra is a multi-language technical-analysis library with a Rust core and bindings for Python, Node.js and WASM, plus a C ABI for C, C++, C#, Go, Java, R and any other C-capable language. Every indicator is an O(1) streaming state machine, so live trading bots and historical backtests share the exact same implementation. This package is the C ABI hub: it compiles the core to a C-compatible shared/static library plus a generated header, so any C-capable language (C, C++, C#, Go, Java, R) links against one artifact instead of re-wrapping every indicator natively.

Install

Grab the prebuilt header + library for your platform from the GitHub releases — each archive has wickra.h, the optional wickra.hpp C++ wrapper, and the shared/static library — or build from source:

cargo build -p wickra-c --release
# -> target/release/libwickra.{so,dylib} or wickra.dll (+ import lib) + a staticlib

Then compile against the header and link the library (cc app.c -I include -L lib -lwickra -lm -o app).

Quick start

#include "wickra.h"

struct Rsi *rsi = wickra_rsi_new(14);              /* NULL on invalid params */
for (size_t i = 0; i < n; ++i) {
    double v = wickra_rsi_update(rsi, prices[i]);  /* NaN during warmup       */
    if (v == v && v > 70.0)                        /* v == v is the NaN check */
        printf("overbought\n");
}
wickra_rsi_free(rsi);                              /* exactly once per _new   */

Every indicator is an opaque handle with the same five functions — _new / _update / _batch / _reset / _free. update is O(1); there is no RAII across the C boundary, so each _new needs exactly one _free, and every function is NULL-safe (a NULL handle yields NaN or a no-op, never a crash). Multi-output indicators (MACD, Bollinger, ADX, …) take a pointer to a #[repr(C)] struct and return a bool. The optional wickra.hpp wraps any handle in a move-only wickra::Handle for exception-safe C++ lifetimes.

Benchmark

benchmarks/throughput.c reports streaming and batch updates-per-second for SMA, ATR and MACD. As the thinnest binding it is the floor of the per-binding FFI overhead — not a cross-library ratio (the same Rust core runs under every binding); see the repository BENCHMARKS.md §3.

cargo build -p wickra-c --release
cmake -S benchmarks -B build && cmake --build build
./build/throughput

Documentation

The full indicator catalogue, guides, quickstarts, and API reference live in the main repository and documentation site:

Wickra ships native bindings for Python, Node.js, WASM and Rust, plus this C ABI hub that any C-capable language (C, C++, C#, Go, Java, R) links against — all exposing the same indicators from the shared Rust core.

Security

Found a security issue? Please don't open a public issue. Report it privately via the affected repository's Security tab ("Report a vulnerability") or email support@wickra.org with a subject line starting [wickra security]. Full policy: https://github.com/wickra-lib/wickra/blob/main/SECURITY.md.

Disclaimer

Wickra is an indicator toolkit, not a trading system. The values it computes are deterministic transforms of the input data — they are not financial advice and do not predict the market. Any use in a live trading context is at your own risk. The library is provided as is, without warranty of any kind.

License

Licensed under either of Apache-2.0 or MIT at your option.