kingchenc
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.
38 lines
1.7 KiB
Markdown
38 lines
1.7 KiB
Markdown
# Roadmap
|
|
|
|
This roadmap describes the project's direction at a high level. It is
|
|
intentionally non-binding: priorities shift with feedback and available time,
|
|
and the authoritative, up-to-date view of planned work is the
|
|
[issue tracker](https://github.com/wickra-lib/wickra/issues). Shipped changes
|
|
are recorded in [`CHANGELOG.md`](CHANGELOG.md).
|
|
|
|
## Status
|
|
|
|
Wickra is **pre-1.0**. The public API is largely stable but may still change in
|
|
minor releases; breaking changes are called out in the changelog.
|
|
|
|
## Themes
|
|
|
|
- **Indicator coverage.** Continue broadening the indicator catalogue across
|
|
families (trend, momentum, volatility, volume, statistics, market profile,
|
|
and more), each with the same streaming/batch parity and test guarantees.
|
|
- **API stabilization toward 1.0.** Settle the public `Indicator` and
|
|
`BarBuilder` traits and the binding surfaces, then commit to semantic
|
|
versioning stability for a 1.0 release.
|
|
- **Performance.** Keep per-tick updates O(1) and maintain the benchmark suite;
|
|
investigate further allocation and cache improvements.
|
|
- **Bindings parity.** Keep the Python, Node.js and WebAssembly bindings — plus
|
|
the C ABI and the C# / .NET binding generated from it — in lockstep with the
|
|
Rust core, including type stubs and platform coverage.
|
|
- **Documentation.** Maintain a deep-dive page per indicator on
|
|
<https://docs.wickra.org>, plus quickstarts and cookbook material.
|
|
- **Project health.** Maintain test coverage, static and dynamic analysis,
|
|
signed releases, and supply-chain monitoring.
|
|
|
|
## How to influence the roadmap
|
|
|
|
Open or comment on an issue, or start with the
|
|
[feature-request template](.github/ISSUE_TEMPLATE/feature_request.md).
|
|
Well-scoped proposals and pull requests are the most effective way to move an
|
|
item forward.
|