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

Seems like an oversight on our part.

I'm imagining that we would

1. Make the default amount of fuel 0 in the CLI
2. Add a --add-fuel <N> option to add N fuel to the store

I think (1) miiiiight be slightly controversial? As an alternative, we would have a --set-fuel <N> option, instead of --add-fuel <N>, and then we would have to ensure that the store gets exactly N fuel rathe

Current behavior

Before autocomplete:

When trying to use chrome's autocomplete, autocomplete appears with a white background, which creates havoc along with PlaceholderText
<img width="385" alt="image" src="https://user-images.githubusercontent.com/3002

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

Describe the bug

The SubMenu component log to console True/False when the key of the submenu is == "

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.

Motivation

Currently, we use a local environment to run the Include What You Use like #1179
However, it will be better to create a workflow for the regular scanning.

Reference: https://github.com/include-what-you-use/include-what-you-use