component-model

component-model copied to clipboard

Async and streamable data segments

3

How should components bundle static assets? We have seen several early incantations of this for WebAssembly modules, e.g. [emscripten file systems](https://emscripten.org/docs/porting/files/file_systems_overview.html). Many languages have a concept of embedding data, e.g....

ricochet

Variant extensions

2

Another "nice to have" as opposed to being anything particularly crucial. I was considering use of variants as error types, as it seems like the best option to have fine-grained...

guybedford

Dictionaries

13

Are dictionaries on the roadmap for the component model? At the moment it seems this requires representation via `list`, where a dictionary could be a relatively straightforward host-level representation over...

guybedford

Top-level JS error mappings

1

For functions that directly return a result, is the expectation that these map to the host-level error handling? This is mentioned briefly as a possibility for JS results in the...

guybedford

Kebab-case definition produces collision when mapped to snake_case

5

The component-model grammar has this for ``: ``` name ::= | - word ::= [a-z][0-9a-z]* | [A-Z][0-9A-Z]* ``` That accepts both "apple" and "APPLE". This leads to collisions when converting...

sunfishcode

Nested interfaces

6

Here is an outline for the various ways in which one could describe nested interfaces in wit. For additional context re: motivation, see [this issue](https://github.com/WebAssembly/component-model/issues/301), though generally what this enables...

macovedj

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...

lukewagner

Tweak syntax for how component-level export identifiers are bound

4

A good observation in #276 is that the way we bind new `$identifiers` in component-level `export` definitions is a bit irregular, being the only place in WAT where we bind...

lukewagner

Caller provided buffers question

33

Last week, [an idea was presented](https://docs.google.com/presentation/d/13FbrlS1mPcG2nhypU6zLCDfw2Ghdmt-Q2xCcfeOLQ0s/edit#slide=id.g2e56144be26_0_259) by which callers could prevent unnecessary intermediate copies using the syntax: read: func(length: u64) -> result<list<u8; ..length>,error-code>; Is there any provision to make this...

badeend

Support `@deprecated` gates in WIT

2

## Motivation Following up on the conversation in https://github.com/WebAssembly/wasi-http/issues/107 (renaming `field-key` to `field-name`), we should support some form of `@deprecated` notation to mark individual items as deprecated. In the linked...

yoshuawuyts