wit-bindgen icon indicating copy to clipboard operation
wit-bindgen copied to clipboard

A language binding generator for WebAssembly interface types

Results 226 wit-bindgen issues
Sort by recently updated
recently updated
newest added

Updates JS integer lowering to match the component model explainer (assuming that WebAssembly/component-model#52 is merged). The main differences are that out-of-range numbers now wrap instead of throwing, and that non-integers...

When generating a rust-compiled-to-wasm module and you want to export things with the witx macro, it's possible to get a pretty confusing error. This Rust code: ```rust witx_bindgen_rust::export!("w1.witx"); use w1::*;...

gen-rust-wasm

Updates the representation of flags in JS to match the component model explainer. Previously, flags were represented as bitfields in JS. This PR changes them to be represented as objects...

We should decide on a workflow for generating changelogs as the need for a more robust release system grows. Since wit-bindgen `main` is composed of commits made from PR descriptions...

I've cleaned up some idiosyncrasies of how `wit-bindgen` represents types, and also some other things surrounding that. The main thing that I've changed in this PR is to distinguish between...

People are going to want to parse WIT from other languages and I've already run into a case where it would be useful to have bindings in Python for writing...

PR #193 merges in an `Opts::standalone` flag intended to assist in generating code into standalone source files, with the ultimate intention being to precompile those files into external crates referenced...

gen-rust-wasm

I use this tool to generate the binding for wasmtime, and now i want to compile assemblyscript code to wasm module and run it in wasmtime, i need `canonical_abi_realloc` code...

When users are consuming generated code in Python, they are not able to tell which integer type a given `int` was or what size a float was. We can make...

gen-wasmtime-py

Given #232 (thanks @Kylebrown9 !) could we make a `0.2.0` tag?