You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<Ws/> <ahref="https://docs.wasmer.io/ecosystem/wasmer/wasmer-features#support-of-features-by-compiler">Wasmer</a> (<sup>1</sup> native support in non-JS hosts)
58
+
||
59
+
| **Unsure**
60
+
| WASI<sup>2</sup> | <Xx/> <Xx/> <Xx/> <No/> <Wt/> <Ws/> | 🔨 | Not a good fit (double-polyfill)
61
+
| Interface Types<sup>3</sup> | | | No DOMString support in MVP
<Ws/> <ahref="https://docs.wasmer.io/ecosystem/wasmer/wasmer-features#support-of-features-by-compiler"target="_blank"rel="noopener">Wasmer</a> (<sup>1</sup> native support in non-JS hosts)
71
+
72
+
<sup>2</sup> WASI is [not a good fit](https://github.com/WebAssembly/WASI/issues/401) for AssemblyScript's use case currently and we would appreciate more cooperation.<br />
73
+
<sup>3</sup> The Wasm CG [has decided](https://github.com/WebAssembly/interface-types/issues/135) that [`DOMString`](https://developer.mozilla.org/en-US/docs/Web/API/DOMString) support (ours and JS's `String`) is out of scope of Interface Types.
0 commit comments