Wickra.Compile 0.1.4

<p align="center"> <a href="https://wickra.org"><img src="https://raw.githubusercontent.com/wickra-lib/.github/main/profile/wickra-banner.svg?v=514-8" alt="Wickra Compile — compile a strategy spec into a standalone deployable" width="100%"></a> </p>

Wickra Compile — C#

Part of the Wickra ecosystem: — for C#. dotnet add package Wickra.Compile — prebuilt native library, no system dependencies.

C# / .NET bindings for the Wickra strategy compiler over its C ABI hub. A Compiler is driven over a JSON boundary, so the manifest it produces is byte-identical to every other Wickra Compile binding.

Install

dotnet add package Wickra.Compile

The native library ships prebuilt per platform under runtimes/<rid>/native/, selected automatically. There is nothing to compile. Targets .NET 8 and later.

The native C ABI library is loaded through a DllImportResolver. For a local build, run cargo build -p wickra-compile-c --release and the test project copies the library from target/release next to the assembly (see the <Content> items in WickraCompile.Tests).

Quick start

using Wickra.Compile;

using var compiler = new Compiler();

var response = compiler.Command("""
    {"cmd":"compile","dry_run":true,"spec":{
      "strategy":{"symbol":"x","timeframe":"1h",
        "indicators":{"f":{"type":"Ema","params":[3]}},
        "entry":{"cross_above":["f","f"]},"exit":{"cross_below":["f","f"]},
        "sizing":{"type":"fixed_qty","qty":1}},
      "target":{"kind":"wasm"},"crate_name":"demo"}}
    """);

Console.WriteLine(response); // response JSON, including manifest.project_hash

Surface

• new Compiler() — construct a compiler handle; it is IDisposable, so wrap it in using.
• string Command(string cmdJson) — apply a command envelope ({"cmd":"...", ...}) and return the response JSON. Commands: compile, targets, version, artifact_bytes, reset.
• static string Version() — the crate version.

A malformed command, an unknown command name, or an invalid spec is reported in-band as {"ok":false,"error":...} (the response JSON), not as an exception.

Determinism

The whole compiler lives once in the Rust core; this binding forwards its JSON verbatim, so a given spec produces the byte-identical manifest here and in every other binding — the exact cross-language golden invariant.

Benchmark

Every binding forwards to the same data-driven Rust core, so what this one adds is the call overhead of [LibraryImport] P/Invoke over the C ABI, not a different result. The core's throughput is measured by the repository's benchmark suite and the nightly bench.yml run; the numbers, the machine and how to reproduce them are in the repository BENCHMARKS.md.

Documentation

The full guide, the spec reference and the API documentation live in the main repository and the documentation site:

• Repository: https://github.com/wickra-lib/wickra-compile

• Docs (guides, spec reference, cookbook): https://compile.wickra.org

• Runnable example: examples/csharp/

• The main project: https://github.com/wickra-lib/wickra-compile

• Documentation: https://wickra.org

Wickra Compile ships native bindings for Python, Node.js, WASM and Rust, plus a C ABI hub that any C-capable language (C, C++, C#, Go, Java, R) links against — all forwarding to the same data-driven, unsafe-forbidden Rust core.

Security

Found a security issue? Please don't open a public issue. Report it privately via the repository's Security tab ("Report a vulnerability") or email support@wickra.org with a subject line starting [wickra security]. Full policy: https://github.com/wickra-lib/wickra-compile/blob/main/SECURITY.md.

Disclaimer

Wickra Compile is a code-generation tool, provided "as is" without warranty of any kind. It generates projects and can invoke cargo to build them — run it only on specs you trust. Nothing here is financial advice; compiled strategies are your responsibility, and trading carries risk of loss.

License

Licensed under either of Apache-2.0 or MIT at your option.