webassembly

It is awkward, but TypeScript officially supports using .js in import specifiers, like so:

import {foo} from './path/to/some/file.js'
console.log(foo)

where ./path/to/some/file.js does not actually exist, but th

~/go/src/go.googlesource.com/go/src/compress/flate $ tinygo test -c compress/flate && ./flate.test
~/go/src/go.googlesource.com/go/src/compress/flate $ go test -c &&  ./flate.test
PASS

Summa

I think it would be helpful to have more example in docstrings on how to use various functions and methods exposed in Pyodide. The general approach could be to,

• have a short description documenting the function/method/class and its parameters/return value
• include an example, ideally that is run as a doctest (we need to figure out how to do this) otherwise those will get outdated in time

In bytecodealliance/wasmtime#2497 (comment) we added support for generating nested modules, and we generate these modules by concatenating strings of WAT and then passing it to Module::new which internally checks for WAT strings and assembles them into Wasm bytes if necessary.

We can make this more efficient, improving the number of test cases we fuzz in a

Current behavior

Might be specific to Samples app, but requires investigation if this sequence of events is handled properly in general.

Expected behavior

Should not cause exception.

How to reproduce it (as minimally and precisely as possible)

1. Open Samples app on Android
2. Press the hardware back button to "close" the app
3. Switch to the app using task switcher on Android (

Related to metering wasm3/wasm3#127 and being able to run a set number of instructions, I'd like to be able to serialize a paused interpreter's state and deserialize it to a new interpreter instance; very roughly,

const interp = new wasm3.Interpreter(module);
interp.interpretNInstructions(100);
const interpState = interp.serializeState();
const interp2 = wasm3.In

Problem

walt-cli package when linking multiple .walt files together can "wrap" the modules in a stand-alone JS module. The resulting module is too large because it serialized the dependency tree with the AST information encoded directly into the output, resulting in a massive amount of js.

Encoding the dependencies into the file is done to ensure the module can be used stand-alone in br

links to missing page:
https://github.com/finos/perspective/blob/master/examples/simple/superstore-arrow.html

Most of the macros exported by seed are undocumented, see: https://docs.rs/seed/0.7.0/seed/#macros
It would be good if at least the most commonly used are documented with an example.

The yew framework allows developers to create web UI in Rust. It could compile Rust code into WebAssembly bytecode that runs inside the browser to render the DOM objects for the UI.

Alternatively, it could compile Rust to native machine code, and run it on a Rust-based web server (actix-web) to generate the HTML elements for the UI ([SSR](https://yew.rs/docs/next/advanced-topic