kingchenc
23d636fd97
Adds a Go binding (`bindings/go`) over the C ABI hub — the second language stecker after C#. ## What's here - **`bindings/go`** — a cgo binding exposing all 514 indicators as idiomatic Go types with `New<Indicator>` constructors and `Update`/`Batch`/`Reset`/`Close` methods. The wrappers in `indicators_gen.go` are generated from `bindings/c/include/wickra.h` (same archetype taxonomy as the C# generator: scalar/batch, multi-output, bars, profile, profile-values, array-input). Opaque handles are freed by `Close()` with a `runtime.SetFinalizer` backstop; pointer arguments are caller-owned, panics never cross the boundary. - **`examples/go`** — the full example suite mirroring C/C#: streaming, backtest, multi_timeframe, parallel_assets (goroutine fan-out), three strategies, and `fetch_btcusdt`/`live_binance`. - **CI** — a `go` job builds the C ABI library, stages it, and runs `gofmt`/`go vet`/`go test` plus the offline examples on Linux, macOS and Windows. - **Docs** — Go 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 binding links the prebuilt C ABI library via cgo (`libwickra.so`/`.dylib`/`wickra.dll` staged under `bindings/go/lib`, gitignored). The native libraries are already shipped per target triple by the existing `c-abi-build` release job; distribution is via the subdirectory module tag `bindings/go/vX.Y.Z` (gated), so `release.yml` needs no new publish job. No Rust crate or `Cargo.toml` change — the Go module is standalone and additive. Not for merge yet (gated, per request).
1.8 KiB
1.8 KiB
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. Shipped changes
are recorded in 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
IndicatorandBarBuildertraits 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 and Go bindings 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. Well-scoped proposals and pull requests are the most effective way to move an item forward.