Daniel Macovei
Daniel Macovei
Currently, when publishing a wit package, the string used at the top of the package declaration in the wit file does not need to correspond to the name or version...
Added instructions for tools that have registry support, (`cargo-component`, `wit`, and `wac`). The tools that have registry support have a few different assumptions about how both WIT packages and components...
Here is an outline for the various ways in which one could describe nested interfaces in wit. For additional context re: motivation, see [this issue](https://github.com/WebAssembly/component-model/issues/301), though generally what this enables...
Wit files that leverage [multiple packages](https://github.com/bytecodealliance/wasm-tools/pull/1577) should be able to be encoded into binary and printed back out with the changes in this PR
This PR enables the ability to describe nested interfaces in wit via the `nest` keyword. ``` package foo:bar; interface baz { nest other:pkg/qux } ``` This would indicate that that...
This PR servers as an initial description of what the desired behavior of an `unlocked-dep` would include. As exemplified in the PR, most language toolchains would probably use it in...
In https://github.com/bytecodealliance/component-docs/issues/245 a user encountered a bump when trying to import functionality from `wasi:http` that I'd guess will occur again. Not sure if this belongs in the subsection on worlds,...
In the Docs SIG today there was a discussion about how to simplify the tutorial to make the sections on composition easier to understand. One point that was brought up...
Now that `cargo-component` uses `wasm-pkg-tools` it can inherit the `wkg.lock` and stop using `Cargo-component.lock` Depends on https://github.com/bytecodealliance/wasm-pkg-tools/pull/124 being merged first.