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.
36 lines
871 B
Markdown
36 lines
871 B
Markdown
---
|
|
name: Feature request
|
|
about: Suggest a new indicator or capability for Wickra
|
|
title: "[Feature] "
|
|
labels: enhancement
|
|
assignees: ""
|
|
---
|
|
|
|
## Problem
|
|
|
|
<!-- What are you trying to do that Wickra cannot do today? -->
|
|
|
|
## Proposed solution
|
|
|
|
<!-- For a new indicator: its name, formula, and the standard parameters.
|
|
Link a reference implementation (TA-Lib, pandas-ta) if one exists. -->
|
|
|
|
## Alternatives considered
|
|
|
|
<!-- Other approaches and why they fall short. -->
|
|
|
|
## Scope
|
|
|
|
- [ ] Affects the Rust core
|
|
- [ ] Should be exposed in the Python binding
|
|
- [ ] Should be exposed in the Node binding
|
|
- [ ] Should be exposed in the WASM binding
|
|
- [ ] Should be exposed in the C ABI
|
|
- [ ] Should be exposed in the C# / .NET binding
|
|
- [ ] Should be exposed in the Go binding
|
|
- [ ] Should be exposed in the R binding
|
|
|
|
## Additional context
|
|
|
|
<!-- Anything else that helps. -->
|