js-types
js-types copied to clipboard
Proposal for adding type reflection to the JS API
See and for details.
[Typed function references](https://github.com/WebAssembly/function-references/blob/b158867a0cb5c24a31ee9a31c2169300bfae7586/proposals/function-references/Overview.md#type-representation) proposes exposing reference types as `{ref: ConsType, nullable: bool}`. Should this pattern also be used for funcref/externref?
Allow both 'initial' and 'minimum' in memory and table constructors to keep it backward compatible
Please see the following test: https://github.com/WebAssembly/spec/blob/master/test/js-api/memory/constructor.any.js#L86
According to the spec[^1], the properties representing the limits are named `minimum` and `maximum`. However, in the overview[^2] of this repository, `min` and `max` are used. This PR updates the...
I'm concerned about the interaction between this proposal and the JSPI, in particular about the behavior of `new WebAssembly.Function(sig, new WebAssembly.Suspending(jsFunc))`. I believe the two specs as they currently exist...
Building the interpreter (running `make -C interpreter`) currently fails with this error: ``` $ make -C interpreter echo >_tags "true: bin_annot" echo >>_tags "true: debug" echo >>_tags ": for-pack(Wasm)" ocamlbuild...
I would appreciate some more clarity (and perhaps also discussion...) on the expected behavior when using `new WebAssembly.Function(inner_func, $sig0)` for the case where `inner_func` has a signature (because it's another...
I'd like to propose transitioning this proposal from Phase 3 to Phase 2/Phase 1. With Wasm 3.0, this proposal is now out of date, and doesn't cover all the types...