wickra/.github/ISSUE_TEMPLATE/performance_regression.md at 23d636fd975d145e51a8e495923475e1ee338f55

Files

T

kingchencandGitHub 23d636fd97 Add the Go binding over the C ABI hub (#228 )

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).

2026-06-09 17:33:37 +02:00

1.6 KiB

Raw Blame History

name, about, title, labels, assignees

name

about

title

labels

assignees

Performance regression

Report a measurable slowdown, memory blowup, or throughput drop.

[Perf] <indicator / API> regressed in <version>

performance

regression

triage

Summary

Affected code path

Indicator / API: e.g. EMA.update
Binding: Rust / Python / Node / Wasm / C ABI / C# (.NET) / Go
Hot loop or one-shot call?

Versions compared

Version	Throughput / latency / memory	Notes
`0.4.1`	`e.g. 12.3 ns/iter`	baseline (Good)
`0.4.2`	`e.g. 38.7 ns/iter`	regressed

Benchmark / reproducer

cargo bench --bench ema -- --save-baseline new

ema/update              time:   [38.5 ns 38.7 ns 38.9 ns]
                        change: [+213.4% +214.8% +216.1%] (p = 0.00 < 0.05)
                        Performance has regressed.

Hardware / environment

Field	Value
CPU	`e.g. Ryzen 9 9950X, AVX2 + AVX512`
OS / arch	`e.g. Linux 6.8 x86_64`
Toolchain	`rustc 1.x.y`
Build flags	`RUSTFLAGS=...`, `--release`, profile

1.6 KiB Raw Blame History