wac
wac copied to clipboard
bytecodealliance
WebAssembly Composition (WAC) tooling
Related to: #43 This feature could/would supplant `wasm-tools component targets ...`. Historically, improving the detail of diagnostics of the `wasm-tools component targets` tool has been quite difficult because of the...
**tl;dr** `wac plug` differs in semantics from `wasm-tools compose -d` for simplicity sake. While a majority of users are likely to only need the simplified semantics of `wac plug`, there...
See https://github.com/WebAssembly/component-model/pull/332 We need to integrate this into the supported WIT subset of WAC.
It would be nice to have some sort of convenience for declaring a `wac_types::Package` from wit files. Essentially replacing this code: ```rust let mut resolve = wit_parser::Resolve::new(); let pkg =...
Upstream change to the proposal: https://github.com/WebAssembly/component-model/pull/338 We should be validating this in `Package::from_file` and `Package::from_bytes` too.
In my usecase, I need to perform several compositions that each have a different "main" component but several util components that are the same (they implement WASI, similar to what...
Tracking issue for decoding wasm files from a previous graph encoding back to a `CompositionGraph`, allowing `wac-parser` to be able to emit a WAC source representation of the graph. As...
https://github.com/zkat/miette/pull/347 landed on Feb 21. Maybe this comment can be addressed now? https://github.com/bytecodealliance/wac/blob/d3f6be29f2629d866be4b1e476b373d7feaf77b5/crates/wac-parser/src/lexer.rs#L466-L479
When instantiating a component, it's probably safe to supply it with additional imports that aren't declared in its world. For example, consider a component that declares an import `foo` in...
