cranelift

rust jit wasm webassembly runtime wasi cranelift sandbox wasmtime

Alex Crichton af2b4e4946 Add initial support for WebAssembly Interface Types (#282 ) This commit adds initial support for [WebAssembly Interface Types][proposal] to wasmtime. This is all intended to be quite experimental, so experimental in fact that even the name of the [proposal] is still in flux. (this has otherwise been known as "host bindings" or "webidl bindings" or "wasm bindings"). The goal of this commit is to start adding support the wasmtime set of crates for WebAssembly Interface Types. A new `wasmtime-interface-types` crate has been added with very basic support for dynamically invoking and inspecting the various bindings of a module. This is in turn powered by the `wasm-webidl-bindings` crate which is shared with the `wasm-bindgen` CLI tool as a producer of this section. Currently the only integration in `wasmtime`-the-binary itself is that when passed the `--invoke` argument the CLI will now attempt to invoke the target function with arguments as parsed from the command line itself. For example if you export a function like: fn render(&str) -> String Then passing `--invoke render` will require one argument on the command line, which is the first argument as a string, and the return value is printed to the console. This differs from today's interpretation of `--invoke` where it is a failure if the invoked function takes more than one argument and the return values are currently ignored. This is intended to also be the basis of embedding wasmtime in other contexts which also want to consume WebAssembly interface types. A Python extension is also added to this repository which implements the `wasmtime` package on PyPI. This Python extension is intended to make it as easy as `pip3 install wasmtime` to load a WebAssembly file with WebAssembly Interface Types into Python. Extensions for other languages is of course possible as well! One of the major missing pieces from this is handling imported functions with interface bindings. Currently the embedding support doesn't have much ability to support handling imports ergonomically, so it's intended that this will be included in a follow-up patch. [proposal]: https://github.com/webassembly/webidl-bindings Co-authored-by: Yury Delendik <ydelendik@mozilla.com>	5 years ago
..
__init__.py	Add initial support for WebAssembly Interface Types (#282)	5 years ago

Alex Crichton af2b4e4946 Add initial support for WebAssembly Interface Types (#282 )

This commit adds initial support for [WebAssembly Interface
Types][proposal] to wasmtime. This is all intended to be quite
experimental, so experimental in fact that even the name of the
[proposal] is still in flux. (this has otherwise been known as "host
bindings" or "webidl bindings" or "wasm bindings").

The goal of this commit is to start adding support the wasmtime set of
crates for WebAssembly Interface Types. A new `wasmtime-interface-types`
crate has been added with very basic support for dynamically invoking
and inspecting the various bindings of a module. This is in turn powered
by the `wasm-webidl-bindings` crate which is shared with the
`wasm-bindgen` CLI tool as a producer of this section.

Currently the only integration in `wasmtime`-the-binary itself is that
when passed the `--invoke` argument the CLI will now attempt to invoke
the target function with arguments as parsed from the command line
itself. For example if you export a function like:

    fn render(&str) -> String

Then passing `--invoke render` will require one argument on the command
line, which is the first argument as a string, and the return value is
printed to the console. This differs from today's interpretation of
`--invoke` where it is a failure if the invoked function takes more than
one argument and the return values are currently ignored.

This is intended to also be the basis of embedding wasmtime in other
contexts which also want to consume WebAssembly interface types. A
Python extension is also added to this repository which implements the
`wasmtime` package on PyPI. This Python extension is intended to make it
as easy as `pip3 install wasmtime` to load a WebAssembly file with
WebAssembly Interface Types into Python. Extensions for other languages
is of course possible as well!

One of the major missing pieces from this is handling imported functions
with interface bindings. Currently the embedding support doesn't have
much ability to support handling imports ergonomically, so it's intended
that this will be included in a follow-up patch.

[proposal]: https://github.com/webassembly/webidl-bindings

Co-authored-by: Yury Delendik <ydelendik@mozilla.com>

5 years ago

__init__.py

Add initial support for WebAssembly Interface Types (#282)

5 years ago