kingchencandGitHub
91f6f67257
The first language stecker on the C ABI hub: a .NET binding exposing all 514 indicators as idiomatic `IDisposable` classes, generated from `wickra.h`. ## What's here - **`bindings/csharp/`** — the `Wickra` .NET 8 package. `[LibraryImport]` source-generated P/Invoke (`NativeMethods.g.cs`) plus idiomatic wrappers (`Indicators.g.cs`), both generated from the committed `bindings/c/include/wickra.h`. The binding owns no indicator maths — it only marshals types across the C ABI. - **Marshalling, verified end-to-end against the native library.** Opaque handles cross as `nint` kept alive per call via a `SafeHandle`; `bool` as `[MarshalAs(U1)]` (Rust `bool` is one byte); a self-correcting `DllImportResolver` validates the loaded library actually exports the Wickra ABI. Tests cover one representative per FFI archetype (scalar, candle, pairwise, multi-output, bars, profile, values-profile, order-book / array-input) plus exact Sma reference values. - **NuGet packaging** — `dotnet pack` produces `Wickra.<version>.nupkg`; the release pipeline stages prebuilt native libraries under `runtimes/<rid>/native/` for six target triples (win/linux/osx × x64/arm64). - **`examples/csharp/`** — nine examples mirroring `examples/c/`: streaming, backtest, multi_timeframe, parallel_assets, three strategies, and fetch_btcusdt + live_binance. - **CI** — a `csharp` job on the three OSes builds the C ABI, tests the binding, and runs the offline examples. **Release** — a gated `csharp-publish` job packs and pushes to NuGet (gated on `NUGET_API_KEY`, independent of the GitHub-release job so a C# hiccup never blocks the C/C++ asset release). - **Docs consistency wave** — README, CONTRIBUTING, CHANGELOG, examples/README, the issue / PR templates, `sync-about.yml`, and `.gitattributes`. The native Python / Node / WASM bindings and the C ABI are untouched; this is additive. Publishing to NuGet stays gated behind the release tag and the secret.
34 lines
788 B
Markdown
34 lines
788 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
|
|
|
|
## Additional context
|
|
|
|
<!-- Anything else that helps. -->
|