wasm
WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable target for compilation of high-level languages like C/C++/Rust, enabling deployment on the web for client and server applications.
Here are 2,633 public repositories matching this topic...
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
Newcomer issues
- copy/v86#431
- copy/v86#333 (add a mute button and/or fix the "requires a gesture" warning. A volume selector would also be nice)
There's a minor issue where holding down and moving the mouse on the screen selects text outside of the screen on FirefoxRetry XHR requests that fail with 5xx or time out, with exponential backoff- Add configuration via url parameters (https://githu
JavaScript Request: Expose Texture methods getWidth(), getHeight(), getDepth(), getLevels(), etc.
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
-
Updated
Nov 19, 2021 - Rust
For now, Object protocol methods are (mostly) thin wrapper of matching vm functions. Because we don't need to have duplicated functions for same features, they need to be moved from vm to object protocol functions.
vmpath:vm/src/vm.rs- object protocol path:
vm/src/protocol/object.rs
The matching vm functions are easy to find because object methods are calling it.
- get_att
-
Updated
Sep 30, 2021 - JavaScript
Summa
-
Updated
Nov 20, 2021 - C
-
Updated
Nov 2, 2021 - JavaScript
-
Updated
Nov 18, 2021
fuzzing: Use `wasm-encoder` rather than generating WAT text and then assembling it in dummy imports
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 {
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
-
Updated
Nov 8, 2021 - Rust
-
Updated
Nov 19, 2021 - C#
-
Updated
Nov 2, 2021 - Go
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.
-
Updated
Nov 15, 2021
-
Updated
Oct 6, 2021 - C++
-
Updated
Nov 20, 2021 - Rust
- Organization
- WebAssembly
- Website
- webassembly.org
- Wikipedia
- Wikipedia
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::Keyshould be