component-model

component-model copied to clipboard

Interface types don't always map to valid Web IDL types

3

Some of the conversions between JS values and interface types are defined in terms of the conversions between JS values and Web IDL types. However, not all of those interface...

Liamolucko

Rationale asynchrony model

3

This week @aturon gave a presentation on asynchrony in the component model. I was surprised by the amount of machinery introduced in https://hackmd.io/NM8WrCMWRPOwq--K1jRQrg?view. Would someone mind elaborating why this direction...

badeend

Possible confusion between the unit type and the 0-tuple

5

Currently interface types has both a `unit` as well as a `tuple` type, and the tuple type can have any number of fields. This raises a possible ambiguity for languages...

alexcrichton

Interaction with the memory64 proposal

6

With the [memory64 proposal](https://github.com/webassembly/memory64) for WebAssembly this will change the internal representation of types in the canonical ABI, notably where strings/lists now have 64-bit pointers and lengths instead of 32-bit...

alexcrichton

Is my mental model of the component-model correct?

3

I think I've seen the following analogies briefly mentioned somewhere, though I don't remember where. Are these correct? ### Instances An "instance" is a Dictionary/Map/Record object, mapping exported names to...

badeend

Spec-defined name section for components

1

Similar to how core wasm has a well-defined `name` custom section I think it would also be good to define one for the component model with all of the types...

alexcrichton

Should all types be exportable?

1

Right now in the current documentation I believe that all types are exportable but no types can be imported. In discussion with @peterhuene this I believe is because it enables...

alexcrichton

Proposal: simple instance lowering?

4

## Overview of current problem Assume there is an interface named `example` with this definition (in `wit`): ```wit func1: function(x: string) -> string func2: function(y: list) func3: function(z: tuple) ```...

peterhuene

WIT Syntax: `interface`

1

Signed-off-by: Brian H

fibonacci1729

WIT Syntax: `interface`

2

# WIT + `interface` Given the proposal to introduce a new top-level [WIT](https://github.com/WebAssembly/component-model/blob/main/design/mvp/WIT.md) syntax (i.e. [`worlds`](https://github.com/WebAssembly/component-model/pull/83)) for describing [component types](https://github.com/WebAssembly/component-model/blob/main/design/mvp/Explainer.md#type-definitions), it has become clear that `*.wit` documents are evolving to...

fibonacci1729