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

This PR sketches out the initial format for WebAssembly Worlds. [Rendered](https://github.com/fibonacci1729/component-model/blob/profiles/design/mvp/WORLD.md) Signed-off-by: Brian H

Many tools might want to add additional metadata to WIT declarations that modify code generation behaviour. A concrete example would be the `async` option of `wit-bindgen-wasmtime` , which marks functions...

My current interpretation of the subtyping rules is that the intention is to be primarily useful when connecting two components together within the same component. When a function call happens...

Currently in [`Binary.md`](https://github.com/WebAssembly/component-model/blob/799a7f7f2819ce7e0cfb9ac76fde2d9c09f10d00/design/mvp/Binary.md) it looks like there's two different ways to alias an outer core wasm type. One is using `core:alias` with `sort` as 0x10/`type`. The other is using `alias`...

Currently the [`Binary.md`](https://github.com/WebAssembly/component-model/blob/799a7f7f2819ce7e0cfb9ac76fde2d9c09f10d00/design/mvp/Binary.md) states: > Validation of alias declarators only allows outer type aliases. Validation of these aliases cannot see beyond the enclosing core type index space. Since core modules...

If WASI is going to use Resource Subtyping, it should probably be rendered here first so that implementations can conform to an official definition/specification of how they work.

enhancement

There was some discussion on recursive types in https://github.com/WebAssembly/interface-types/issues/137. My takeaway was that recursion would be hard to specify with adapter functions. With adapters punted to a post-MVP phase ,...

enhancement

This issue was originally discussed in https://github.com/WebAssembly/component-model/issues/9 and I believe the intention was that "degenerate cases" of pairing lower/lift would turn into a function that immediately traps. Interpreting the current...

Eventually, this may be expressible via stack unwinding.

TLDR, these proposed changes: - Allow function parameters, record fields and variant case payloads to have default values, as long as they're constant. - When subtyping; allow variant cases to...