Luke Wagner

`ArrayBuffer`s and typed array views are, but not necessarily a future `sliceref` that gets added as a first-class wasm reference type from which bytes can be loaded and stored. The...

Yup! That's the idea at least. Currently in the explainer, `string-to-memory` takes an `f` that maps byte length to a pointer, but the `f` is restricted to be a wasm...

I realized a problem with the above approach: if what we're trying to do is optimize calls into a native runtime (e.g., a native impl of the `read()` call mentioned...

True, but I think that use case is best addressed by either [multi-memory](https://github.com/webassembly/multi-memory) + memory imports or, to support dynamic acquisition of buffers, a first-class core-wasm "slice reference" that can...

IIUC, this PR adds surprising GC implications: If I have a shared `Memory` object `m` and a `WeakMap` `w`, and I `w.set(m, 42)`, then as long as `m`'s underlying buffer...

Sorry, I'm not sure I understand the question. In case it helps: the idea is that `(flags "a" "b" "c")` logically expands to a variant `(variant (case "a") (case "b")...

That's a good question. I think, in general, versioning is a problem that needs to be solved at a higher level, such as the build tools that perform semver resolution...

Great point! I've wondered about this too. The benefit (that you're probably also imagining) of having an explicit abbreviation is that each language would have the opportunity to bind `time`...

Great question! Indeed, pondering this question is what led me to initially file [module-linking/#12](https://github.com/WebAssembly/module-linking/issues/12). What I ultimately realized is that one can break this cycle by splitting out memory+alloc into...

The question here is more at the spec level: if we're specifying the way that adapter code is linked with core code in terms of Module Linking, and Module Linking...