kingchenc
d59cd44043
* docs: standardise language naming and add binding security sections Canonical binding list everywhere: Rust, Python, Node.js, WASM, C, C++, C#, Go, Java, R. Use C# (not .NET) as the language label, WASM (not WebAssembly) in prose, and frame the C ABI as a hub rather than a list item. - Bump stale indicator counts (200+ -> 514) and family count (sixteen -> twenty-four) in the Node/Python/WASM and docs READMEs. - Add a short Security section to all eight binding READMEs. - Relabel benchmark rows (C -> C / C++, C# / .NET -> C#). - Fix the 'language stecker' wording in the C#/Go/R API intros. - Documentation only; no code or public API changes. * release.yml: extend install snippets and expose version output Add the missing registry installs to the release body (dotnet, go, Gradle/ Maven Central, r-universe) alongside cargo/pip/npm, and expose a v-stripped 'version' output from the tag step for the Gradle coordinate. Also fix the C-ABI language order in the assets note (C# before Go). * release.yml: correct the release body (10 languages, all registries) Reframe the tagline to '10 languages' (native Rust/Python/Node.js/WASM + a C ABI hub for C, C++, C#, Go, Java, R) instead of '4 language registries', note that C#/Java/Go/R publish to NuGet/Maven/Go/r-universe via their own jobs, and tidy the Node.js label and the C-ABI hub list.
890 B
890 B
name, about, title, labels, assignees
| name | about | title | labels | assignees | |
|---|---|---|---|---|---|
| Question / usage help | Ask how to do something with Wickra. For open-ended discussion prefer GitHub Discussions. | [Question] <short description> |
|
Note
If this is open-ended ("which indicator should I use for X?") please use Discussions instead — issues are for actionable items.
What are you trying to do?
What have you tried?
import wickra as ta
...
What's confusing or blocking you?
Environment (Only if relevant)
- Wickra version:
e.g. 0.4.2 - Binding:
Rust / Python / Node.js / WASM / C / C++ / C# / Go / Java / R