This is about:

• Other (Important Tips)

Component communication might deserve a dedicated page.

Ancestor -> Descendant

straightforward: passing props. Using a context if the descendants can be too deep down the tree.

Descedant -> Ancestor

This is not very obvious. In fact, two people asked the same question on Discord in one day. And personally, I had no clue either despite h

fitDataset() expects a Dataset that produces elements of a certain shape, with matching batch sizes etc., and throws errors (from standardizeDataIteratorOutput()) when the conditions are not met. These errors should be tested.

It would be helpful to be able to change the name of the 9p file share.
https://github.com/copy/v86/blob/4eb1e5035e91490c5aeebab45553d5043cd84b95/lib/9p.js#L82

For dynamically generating mount tags:

/**
 * @param {string} mountTagName
 */
function genMountTagArray(mountTagName) {
    /**
     * @type {Number[]}
     */
    let _mountTagArray;
    Array.from(mountTagName

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

See e.g. #2570. Some of the unit tests there with "wrong error message" should be somewhat easy to fix - just correct the error message we have to match CPython's. Others might be trickier, since you'll need to add diagnostics to recognize bad syntax and give a more detailed error than "unexpected token". Also, I think around half of them could be fixed just by adding "invalid syntax" in the messa

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

Tracking issue for improving the egui docs. Other suggestions for improvements welcome!

All doc-examples need to be part of the doctests (i.e. they should never be marked ignore, though no_run can maybe sometimes be motivated).

egui

The crate-level docs for egui (at https://docs.rs/egui generated from egui/src/lib.rs) sh

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

Motivation

I am using the following pattern to efficiently initialize a large buffer inside wasm memory from JavaScript without copies (see #1079 for full motivation):

#[wasm_bindgen]
pub struct WasmMemBuffer {
    buffer: Vec<u8>,
}

#[wasm_bindgen]
impl WasmMemBuffer {
    #[wasm_bindgen(constructor)]
    pub fn new(byte_length: u32, f: &js_sys::Function) -> Self {
  

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

It will be very nice to have a read only line edit or text edit that is enabled but does not allow users to edit its content it only allows them to select text and copy it. Also currently there is no context menu shown when right clicking on a text edit.

Specific Demand

When resolving assets, we should determine of the current program is contained within a bundle. If it is, then we should cananocalize the asset differently to be relative to the .app/.deb/.rpm/.exe for a smoother distribution experience.

• macOS

These targets do not provide a straightforward way of bundling assets. I've opted to make it the asset dir configu

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.