webassembly

~/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

On which page?

https://platform.uno/docs/articles/guides/uno-material-walkthrough.html

What's wrong?

Step 2 within the "Section 2: Using Uno.Material library" section makes reference to Chip/ChipGroup/Card/Divider which have now all been moved to the Uno.Toolkit.UI.Material package.

These changes will also need to be reflected in the referenced UnoMaterialSample, an issue tracking

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

I will take care of this

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

Motivation

In WasmEdge, we already support JavaScript, NPM packages, ES6 modules, and even using Rust to implement JS APIs.

However, one of the most commonly requested features is full node.

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.