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.
57 lines
1.5 KiB
Markdown
57 lines
1.5 KiB
Markdown
---
|
|
name: Bug report (Detailed)
|
|
about: Long-form bug report with environment matrix, minimal reproducer, and expected-vs-actual sections.
|
|
title: "[Bug] <short description>"
|
|
labels: ["bug", "triage"]
|
|
assignees: []
|
|
---
|
|
|
|
## Summary
|
|
|
|
<!-- One or two sentences. What did you expect, what happened instead? -->
|
|
|
|
## Affected binding
|
|
|
|
- [ ] Rust crate (`wickra`)
|
|
- [ ] Python (`pip install wickra`)
|
|
- [ ] Node.js (`npm install wickra`)
|
|
- [ ] WebAssembly
|
|
- [ ] Docs / examples only
|
|
|
|
## Environment
|
|
|
|
| Field | Value |
|
|
| -------------------- | -------------------------------------- |
|
|
| Wickra version | `e.g. 0.4.2` |
|
|
| Binding version | `e.g. python 0.4.2 / node 0.4.2` |
|
|
| OS / arch | `e.g. Windows 11 x86_64, Linux glibc` |
|
|
| Rust toolchain | `rustc --version` (If building from source) |
|
|
| Python / Node / .NET version | `python --version` / `node --version` / `dotnet --version` |
|
|
|
|
## Minimal reproducer
|
|
|
|
<!--
|
|
Paste the smallest possible code snippet that triggers the bug.
|
|
If the input data matters, attach a CSV/JSON or paste a few rows inline.
|
|
-->
|
|
|
|
```python
|
|
# or rust / js
|
|
import wickra as ta
|
|
...
|
|
```
|
|
|
|
## Actual output
|
|
|
|
```
|
|
<paste stack trace, panic, wrong values, etc.>
|
|
```
|
|
|
|
## Expected output
|
|
|
|
<!-- What should the indicator / API have returned? Reference a paper, TA-Lib, or another implementation if possible. -->
|
|
|
|
## Additional context
|
|
|
|
<!-- Logs, screenshots, links to related issues, anything else useful. -->
|