component-model icon indicating copy to clipboard operation
component-model copied to clipboard

Repository for design and specification of the Component Model

Results 181 component-model issues
Sort by recently updated
recently updated
newest added

The `post-return` canonopt provides a way for components to clean up allocated result values after the caller has read them. It would also be valuable to provide components a way...

I have a wit package that I am evolving over time with *some* interfaces changing and others staying the same. I'm running into an issue where a world definition for...

As far as I see, this proposal describes components interacting with each other and the host. How would linking components with a non-component Wasm module look like? Could we use...

I propose that the Wit format use `///` comments, rather than `//`. Wit itself [no longer has non-documentation comments](https://github.com/WebAssembly/component-model/issues/273), however multiple projects are looking at using Wit as a base...

Resource types don't currently have the ability to define constructors as having custom result return error types. For this reason, custom static constructors are likely usually preferable for resources since...

The concept of a "World" in WIT describes something larger than what a `component` type defined in the Wasm Component Model needs. Thus it's no longer precise to say a...

I was wandering, now that resources/ownership/borrowing/etc are properly part of the component model; In what way are closures not "just" single-method resources? Can they piggy back off of the semantics...

I finally did an end-to-end read of all (well, most of) the docs in this repo. Since GH doesn't offer a means to comment on committed files, I created a...

In order to allow for future strict parsing of doc comment annotations, we could reserve a pattern for annotations now (without necessarily defining any valid annotations). One common approach is...

The Component Model does not currently allow you to refer to exported types in imports, which feels asymmetric given that one can easily refer to imported types in exports. This...