Luke Wagner

Split 'use' inside worlds into 'use import' and 'use export'

13

This PR proposes to change how `use` works inside WIT `world`s, based on some initial discussion in [wit-bindgen/#822](https://github.com/bytecodealliance/wit-bindgen/issues/822). Currently, `use` can be used with the same syntax in both `interface`s...

Sketch: allow a variable number of imports/exports of fixed type in Wit

20

## Motivation Let's say I'd like to build a component that consumes 3 configuration values `a`, `b` and `c` (which in a [12-factor app](https://12factor.net/config) I'd take as 3 environment variables)....

Consider allowing caller-supplied buffer optimization for return values

1

Based on discussions in [wasi-http/#8](https://github.com/WebAssembly/wasi-http/issues/8), we should consider a return-value optimization that avoids calling `realloc` by instead allowing the core wasm caller to supply a (buffer, length) `i32` pair as...

Consider adding second initialization phase after `start`

9

This issue captures the motivation, summary and sketch of an idea for improving how snapshots work in the component model. ## Motivation There are a number of scenarios where we'd...

Proposal to change WASI to stand for "WebAssembly Standard Interfaces"

9

As discussed in the WASI meeting [today](https://github.com/WebAssembly/meetings/blob/main/wasi/2023/WASI-10-19.md), the proposal is to change "WASI" to stand for "WebAssembly Standard Interfaces" (from "WebAssembly System Interface" today). This reflects two important properties of...

Update Producers Section to match #93

3

As discussed in [#93/comment](https://github.com/WebAssembly/tool-conventions/issues/93#issuecomment-459879563) and the recent [CG meeting](https://github.com/WebAssembly/meetings/blob/master/2019/CG-02-19.md#update-on-producers-section-tool-conventions93-points-to-likely-non-use-in-practice-and-so-next-steps-would-be-to-either-remove-or-soften-wording).

consider adding flag to the WebAssembly.Function that passes first argument as JS receiver

2

At the moment, the JS API [specifies](https://webassembly.github.io/spec/js-api/index.html#run-a-host-function) that, when calling a host function, `undefined` is always passed as the receiver. With the addition of `externref`, it would otherwise be possible...

Consider optimizations to reduce the number of host calls

1

While host calls are pretty fast these days, it's still useful to consider optimizations to reduce their number per request for really low-latency scenarios. This has come up in two...

Spinning out from [this comment](https://github.com/WebAssembly/wasi-http/pull/3#discussion_r1123503363), we should discuss what the right set of variant cases are for [`error`](https://github.com/WebAssembly/wasi-http/blob/f72bd4c19b929f677639821fc472aa9626dcb823/wit/types.wit#L32-L37). Ideally, we'd be able to align with something in the HTTP spec,...

Currently function types are slightly asymmetric with results having an extra single-unnamed-result option. As #356 points out, we could make params and results fully symmetric by saying that both could...