Randy Reddig

I’m working on the Go bindings for WASI Preview 2 and the Component Model. The `ipv4-address` and `ipv6-address` types seem to be reasonable justification for fixed-with array types. ```wit type...

Monotypic `tuple`s implemented as Go arrays here: https://github.com/ydnar/wasm-tools-go/pull/43/commits/be654cd4a90a85d3b8e11e7dbc764a50eae5c5a9 

I think the form of `list` might be confusing, implying that a fixed-length array would despecialize into a `list`, when in fact it has a completely different ABI representation (pass-by-value,...

> > * Monotypic tuple would despecialize into fixed-length arrays of type T. > > > > That's not what you want. Tuples are accessed with a static index and...

This thread is about [Rust](https://doc.rust-lang.org/std/primitive.array.html) and [Go](https://go.dev/ref/spec#Array_types)-style fixed-length arrays, which are value types, not a `list` with a fixed length, which would be represented as a slice or vector in...

Having been bit by this a couple of times, I’m sympathetic to both sides of the argument for and against implicit imported types. I appreciate the discussion here. > A...

@alexcrichton thanks for the feedback. In your mind, what is the concrete proposal now? FWIW, I was thinking about having the warning logic live in `wasm-tools`, perhaps in the `wit-parser`...

I guess we could add sockets to wasip2

Can we also update the documentation here? https://tinygo.org/docs/reference/usage/subcommands/ ``` Compile the given program. The output binary is specified using the -o parameter. The generated file type depends on the extension:...

The Component Model never calls free on these allocations. We'd need some way to assert ownership of them so the GC can free them later.