Soni L.
Soni L.
The APIs should require a named "context", tho it can be empty for POSIX runtimes. Then the CLI for "granting access" would take the context like so: ```text --allow-outbound=postgres@tcp://my.postgres.example:5432 --allow-outbound=https@tcp://*:443...
See also #156, #164, WebAssembly/wabt#1972 and WebAssembly/wabt#2161. Yes, linear memory as seen from wasm is always little-endian. But how should the *host* see it? `wasm-c-api` currently assumes the host is...
See also #156 A "high-level" memory API, with operations like "read_u32", "read_bytes" and so on, would be highly appreciated. Unlike the raw memory API, it would automatically convert addresses/endianness as...
The order of trinket lifecycle events appears to be tick -> onEquip -> tick -> tick -> ... -> tick -> onUnequip. It would be nicer if it were onEquip...
-m is a python standard (PEP 338) and we should support and encourage it. best way to do that is to defer to it when asked to. we should ideally...
So if I type in "headache" but don't click the dropdown, it should just work.
Chasing https://crbug.com/oss-fuzz/51561 Let's see if this breaks anything... The issue only triggers if both conditions are true: - Multi-memory is enabled - Alignment (masked) is between 32 and 63
Please add refactoring to the list.
So let's say I have an IPv4-only machine, and an IPv6-only machine, and I wanna peer-to-peer some files between them, using dat. In a perfect world, both machines would have...