wit-bindgen
wit-bindgen copied to clipboard
A language binding generator for WebAssembly interface types
I can envision uses cases where there are "setter" functions on a resource: ```witx resource person { get_name: function() -> string set_name: function(name: string) } new_person: function(name: string) -> person...
Would be nice not to have them, or at least suppress them. I'm dealing with other things at the moment, but figured I should post this for posterity. ``` warning:...
Some WIP docs that make it easier for users to tell what's supported the language(s) they're interested in. Looking for feedback on the general idea of these docs before I...
Just wanted to open an issue here, about adding support for Ruby as a guest language, i.e. "compiling" ruby down to a WebAssembly component. *** *Note:* This is not about...
This PR is an implementation of `async` witx functions for Wasmtime. This is a significantly different design than what's present today for sync bindings or sync-wasm-but-actually-invoked-`async` bindings. Instead the support...
This implements the changes mentioned in https://github.com/bytecodealliance/witx-bindgen/issues/85#issuecomment-945938217 for switching `witx2`'s `old-witx-compat` parser back to using the `witx` crate from crates.io. Fixes #85.
Currently when the same type is imported multiple times into a WITX module by `use` statements, an error occurs saying that the type is defined twice. Example: **a.witx** ``` type...
I started this work as a hackathon project. It currently can only work with integer functions for both import/export. It's not nearly half done yet, but I want to put...
I'm opening this issue to document my thinking as a result of trying to resolve issues like https://github.com/bytecodealliance/wit-bindgen/issues/214, https://github.com/bytecodealliance/wit-bindgen/issues/34, and https://github.com/bytecodealliance/wit-bindgen/issues/201. I mentioned a number of issues with the current...
There are some use cases that require a host to know some information about the module that invoked it. Examples include access to secrets, or maintaining separation of data in...