Problem
I am returning to WebGL work after some time away (with Vulkan) so may be misinterpreting something here, but...
The WebGL example loops through the render_gl function every frame. Therefore it's recompiling the shaders, linking them, all of this work that doesn't need to be repeated in the render loop.

Steps To Reproduce
Steps to reproduce the behavior:
Start the app as

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

Feature

Our set.update uses IterNext for iterating given args and update the set contents (makes sense).
But this makes incompatibility with cpython.
cpython's implementation is converting given args to tuple and uses get_size and get_item.
As these method does not go through the iternext, there is no exception if the set is mutated during update.

Python Documentation

h

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

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

Summa

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

Having a callback for when the selected element is changed would be useful, for similar reasons to TextEdit/LineEdit: validation, updating buffers, or the rest. I imagine that it would be something like selected(int) with int being the index, though LineEdit emits a simple callback without arguments so there may be a tradeoff I'm missing (an int should be easier to pass around on the oth

Specific Demand

Like use_future, except instead of taking a Future<Output = T>, takes a futures::Stream<Item = T>

Bug type

Component

Component name

MudTextField

What happened?

When creating a MudTextField component and adding a mask to it through the Mask property and setting this component to ReadOnly = true, it still allows to change the field content, the typing cursor is not shown, but it is allowed to type and change the content.

Expected behavior

It is expected that when informing