component-model

component-model copied to clipboard

Give components their own file type

6

The name of this issue might be a little narrow but I wanted to make it clear what I am really suggesting, currently component model is dissambiguated from regular wasm...

spotandjake

Allow exporting types directly worlds without interface

1

Components are also able to directly export types, so it is just a temporary WIT limitation that you're not able to define and export the math-class enum directly in the...

jcbhmr

Enhancing the Canonical ABI with Finer-Grained, Performant Type Layouts for IoT and Performance-Sensitive Environments

6

I acknowledge and appreciate the significant progress made by the Component Model (CM) and its Canonical ABI in resolving cross-language interoperability challenges within the WebAssembly ecosystem. The current design, which...

snowyu

Make 'async' part of the function type, not a hint

11

This PR moves `async` from being a hint that is textually mangled into function names to an optional effect type that is part of a function type. WIT is not...

lukewagner

Consistent version syntax

4

Currently, WIT [package names] put the version after the package name: ```wit package wasi:[email protected]; ``` However, WIT [`use` statements] and similar things put the version after the interface: ```wit use...

sunfishcode

Use formal wit syntax within doc?

1

I noticed that for explaning `event` in explainer, it is written as: ```wit variant event { none, subtask(subtask-index, subtask-state), stream-read(stream-index, stream-result), stream-write(stream-index, stream-result), future-read(future-index, future-read-result), future-write(future-index, future-write-result), task-cancelled, } ```...

peter-jerry-ye

Optional Imports Phase 1: Tooling Conventions

7

Here I'd like to write up the result of some discussion that was had today about optional imports. In the fullness of time optional imports is expected to be a...

alexcrichton

Logo

1

I wanted to have a logo for the component-model for a presentation ([Slides](https://github.com/birneee/2025-noms-wace-comp-net-stack-wasm-quic/blob/main/Exploring%20Composable%20Network%20Stacks%20from%20Isolated%20Components%20with%20WebAssembly%20and%20QUIC.pdf )). So, I decided to create one myself: I’d be happy to contribute this logo to the...

birneee

This issue is a sibling of https://github.com/WebAssembly/wasi-testsuite/issues/181. Wasmtime currently has its own set of component model async tests written in Rust. With an eye on portability, we should upstream these...

yoshuawuyts

If Core WebAssembly eventually gets some form of `memory.{map,unmap}` instruction from the [memory-control proposal](https://github.com/WebAssembly/memory-control), especially [this variant](https://github.com/WebAssembly/memory-control/issues/21) of the [mappable sub-proposal](https://github.com/WebAssembly/memory-control/blob/main/proposals/memory-control/mappable.md) that avoids some of the challenges with native `mmap()`,...

lukewagner