wasm

Yew has recently got support for keyed elements, but the documentation lacks any mention of them. A mention should be added in the website, the doc of yew::virtual_dom::key::Key should be

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

Problem:
After using Engine.createTextureFromKtx/jpeg/Png, I need to query the texture width and height so I can generate proper UV coordinates for font display.

Proposed solution
Expose the Texture.getWidth(), getHeight(), etc. methods to get texture information. I currently only need width and height, but I can see usage cases for many of the other "getters" available in the C++ in

It would be nice to also have some sort of screenshot functionality for text mode too. A not-too-complicated way to do it may be extracting the text_screen outerHTML to pop it into a data:text/html with the necessary styles.

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

Current behavior

When I removed the status bar by adding those 4 lines in the style.xml

<item name="android:windowTranslucentStatus">false</item>
<item name="android:windowTranslucentNavigation">true</item>
<item name="android:windowDrawsSystemBarBackgrounds">true</item>
<item name="android:statusBarColor">@android:color/transparent</item>

Applying `VisibleBoundsPadding

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 {
  

When passing Wasm function to the host as a callback, it's passed as an index in the table.
Wasm3 needs to provide an API to call such functions.

Describe the bug

![image](https://user-images.githubusercontent.com/25119211/125054605-fc934600-e0d8-11eb