Dan Gohman

Do we have any use cases that need atomic behavior? One of the original motivations for adding `splice` was for implementing `std::io::copy` in Rust, and Rust's API doesn't guarantee atomic...

Could you say more about why first-in-first-ready-out order would be useful? It's nondeterministic whether two events happening around the same time are reported in the same `poll` call or in...

Implementations based on Unix-style `poll` or similar won't have information about what order events that occur in the same call happen in, so it seems like it'd be difficult to...

> Process a single chunk of bytes bigger than what the host runtime sandbox allows us to allocate It's unclear how we might meet this requirement, with any approach. For...

I think the question of how to negotiate chunk/buffer sizes is separable from the question of callback vs. polling (vs. integrated async). For chunk/buffer size negotiation, in what situation would...

There is parsing support for the wit syntax in wit-bindgen, but the canonical ABI implementation is not complete yet.

Yes, it sounds like this is a handle that the program should declare as an input argument, though the specific mechanisms for doing this aren't implemented yet.

Yes, that's right. So we should document what happens if you're using bindings like C and you're using a handle after it's been dropped.

Wasm indeed doesn't currently have read-only memory segments. There's the [beginning of a proposal](https://github.com/WebAssembly/memory-control/blob/main/proposals/memory-control/Overview.md), but it's early.

Our main concern with adding targets that aren't in upstream Rust is that once we add a string, it's awkward to change its meaning or to remove it, if it...