kingchencandGitHub
b7ef63400d
Adds an R binding (`bindings/r`) over the C ABI hub — the third language stecker after C# and Go, reaching the hub through R's native `.Call` interface (not extendr). ## What's here - **`bindings/r`** — an R package exposing all 514 indicators as constructors that return a `wickra_indicator` object with generic `update`/`batch`/`reset` methods. The C glue (`src/wickra.c`) and R wrappers (`R/indicators.R`) are generated from `bindings/c/include/wickra.h` (same archetype taxonomy as the C#/Go generators: scalar/batch, multi-output, bars, profile, profile-values, array-input). The opaque handle is an R external pointer freed by a registered finalizer; multi-output returns a named vector (`NA` at warmup), bars a matrix, profiles a list. - **`examples/r`** — the full example suite mirroring C/C#/Go: streaming, backtest, multi_timeframe, parallel_assets (`mclapply`), three strategies, and `fetch_btcusdt`/`live_binance`. - **CI** — an `r` job builds the C ABI library, installs the package, runs the `testthat` suite and the offline examples on Linux, macOS and Windows (`R CMD check` is clean: 0 warnings, 0 notes). - **Docs** — R added to the README languages table, project layout, building/testing, CONTRIBUTING binding table + regenerate note, ARCHITECTURE, examples index, issue/PR templates, the About-description template, and the other binding READMEs. ## Linking / distribution The package compiles a thin `.Call` glue layer against the prebuilt C ABI library (header via `WICKRA_INCLUDE_DIR`, library via `WICKRA_LIB_DIR`). On Windows the package's own `wickra.dll` would collide with the C ABI's `wickra.dll`, so `configure.win` stages a renamed copy (`wickra_abi.dll`) and builds an import library referencing it; `install.libs.R` bundles the DLL and `.onLoad` puts it on the load path. On Linux/macOS the rpath locates the shared library. No `release.yml` change — R is distributed via r-universe / source install (gated). No Rust crate or `Cargo.toml` change — the R package is standalone and additive.
55 lines
1.6 KiB
Markdown
55 lines
1.6 KiB
Markdown
---
|
|
name: Performance regression
|
|
about: Report a measurable slowdown, memory blowup, or throughput drop.
|
|
title: "[Perf] <indicator / API> regressed in <version>"
|
|
labels: ["performance", "regression", "triage"]
|
|
assignees: []
|
|
---
|
|
|
|
## Summary
|
|
|
|
<!-- Which code path got slower, by how much, and since when? -->
|
|
|
|
## Affected code path
|
|
|
|
- Indicator / API: `e.g. EMA.update`
|
|
- Binding: `Rust / Python / Node / Wasm / C ABI / C# (.NET) / Go / R`
|
|
- Hot loop or one-shot call?
|
|
|
|
## Versions compared
|
|
|
|
| Version | Throughput / latency / memory | Notes |
|
|
| -------- | ----------------------------- | ----- |
|
|
| `0.4.1` | `e.g. 12.3 ns/iter` | baseline (Good) |
|
|
| `0.4.2` | `e.g. 38.7 ns/iter` | regressed |
|
|
|
|
## Benchmark / reproducer
|
|
|
|
<!--
|
|
Paste the criterion / pytest-benchmark / hyperfine command and its output.
|
|
For one-off measurements, include the timing snippet inline.
|
|
-->
|
|
|
|
```bash
|
|
cargo bench --bench ema -- --save-baseline new
|
|
```
|
|
|
|
```
|
|
ema/update time: [38.5 ns 38.7 ns 38.9 ns]
|
|
change: [+213.4% +214.8% +216.1%] (p = 0.00 < 0.05)
|
|
Performance has regressed.
|
|
```
|
|
|
|
## Hardware / environment
|
|
|
|
| Field | Value |
|
|
| ------------ | -------------------------------------- |
|
|
| CPU | `e.g. Ryzen 9 9950X, AVX2 + AVX512` |
|
|
| OS / arch | `e.g. Linux 6.8 x86_64` |
|
|
| Toolchain | `rustc 1.x.y` |
|
|
| Build flags | `RUSTFLAGS=...`, `--release`, profile |
|
|
|
|
## Suspected cause
|
|
|
|
<!-- Optional. Link the commit / PR if you've bisected it. -->
|