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 has been discussed. Formally, creating an issue for it. Currently, we lose comments / docs from Wit text formats when compiling to the binary Wasm component file format. This...

In components where the post return function doesn't need to know which values being returned because (e.g. the entire bump allocator is reset) the current requirement that the type of...

Rust has fixed length arrays whose type is written as `[u8;32]` for a 32-byte array. You can achieve this in the current wit specification by doing `tuple` (with 32 `u8`s)....

enhancement

Currently the [projection rule](https://github.com/WebAssembly/component-model/blob/main/design/mvp/Explainer.md#import-and-export-definitions) for import names looks like: ```ebnf projection ::= '/' label ::= | '-' ``` This prevents projections for exports using the `interfacename` format, as these cannot...

In Wit, a "world" corresponds to a component. This took me too long to grasp, because "world" is a strange word for it. "World" has a notion of expanse, plurality,...

Remove the restriction on component start functions calling imports. This allows start functions to run artbitrary user code. And, adjust the 🪙 to include start functions in the MVP, and...

Currently, in the docs and corresponding tooling, package namespaces and names can include a mix of lowercased and uppercased characters, such as `MY-namespace:some-PACKAGE` is valid. As we are looking at...

As a newcomer coming to the Component Model, I was struggling to understand what a ID _meant_ in the context of a WIT file. To help myself and others following...

For additional details and related information, please refer to https://github.com/bytecodealliance/wit-bindgen/issues/815

As of preview2, the NaN-canonicalization rules have been relaxed and so in preview 2 the set of semantic values of `float32` is the same the set for core wasm `f32`...