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

Very minimal adaptation to the new wasm32/64 offset calculation of wit-parser, the generated code is likely still incorrect as the default Display implementation isn't language independent.

I generated a very large enum (it's the icon set https://lucide.dev/icons/) . So I have 1424 cases, but sadly it breaks with `wit-bindgen` with the following error: ``` Caused by:...

the `lib.rs` in `teavm-java` seems to have a number of `todo!` macros currently, which prevent bindings being generated for any `.wit` files containing resource types.

Per https://github.com/dotnet/runtimelab/pull/2614#discussion_r1700019060, `Unsafe.Write` and `Unsafe.As` might be more efficient than `BitConverter.TryWriteBytes` and `BitConverter.To*`, respectively.

gen-c#

Per https://github.com/dotnet/runtimelab/pull/2614#discussion_r1699995101, `List` parameters are often unnecessarily restrictive -- callers might want to pass collections of other types without converting them to `List`s first.

gen-c#

Per https://github.com/dotnet/runtimelab/pull/2614#discussion_r1699988599, using `stackalloc` would likely be more efficient and avoid the need for GC pinning.

In https://github.com/bytecodealliance/wit-bindgen/pull/972 the default for whether bindings would be generated for foreign (i.e., not in the same package as the target world) types was flipped from being generated by default...

When trying to create bindings for a package with multiple worlds, one has to choose which world to target. It'd be great if the error message printed when no choice...

I'm trying to create a wit interface, a type(record) is re-using another type(record) from wasi-http I'm using wasmcloud dev tools, but still the error occurs on the bindgen macro >...

Currently, `rust` bindgen inserts stubs for Wasm imports on native targets, which simply panic. I'd like to discuss possibilities for making this configurable or perhaps define a convention of some...