Dave Bakker

Some other examples: Wasi-http's [`error-code`](https://github.com/WebAssembly/wasi-http/blob/main/wit/types.wit#L85) contains a catch-all item, which to me signals this enum "wants" to be non-exhaustive: ``` /// This is a catch-all error for anything that doesn't...

In terms of subtyping; one consideration is whether subtyping should be a toolchain or a runtime/link-time concern. If we're aiming for the toolchains to handle it, then the ABI is...

> We could also allow multiple partial reads of the same validx so that a single logical list value could be read into multiple non-contiguous segments (think readv()) Another use...

> The host could eagerly retrieve the lazy value before passing it on, convert it and then pass the calculated length in the new encoding along. I suspect the special...

For reference: https://github.com/WebAssembly/interface-types/issues/146. I think that issue was raised before the existence of tuples, though.

Do you have a specific use-case that tuples can't handle?

In addition to an upper bound, could we also add a lower bound, like `list`?

Indeed to indicate a list may not be empty: --- https://github.com/WebAssembly/wasi-io/blob/285a31442f687a5ceee86044f9f2b0a9e2beae21/wit/poll.wit#L34C4-L46C57 ```wit /// This function traps if either: /// - the list is empty, or: /// - the list contains...

All in all: this seems sensible to me. The concept of "errors" are definitely ubiquitous enough to warrant special casing in the component model. --- > With this type, result...

> I think error payloads can only include pure (stateless, identity-less) values, which rules out handles, futures, streams and buffers Okay👍. Out of curiosity: why's that?