Randy Reddig
Randy Reddig
Is there a path to evolving the format of this section? Eg textual WIT, or JSON, etc?
If the content is just a component, is this new command necessary? E.g. can the content of the custom section be created with `component new` from a single WIT file?
Verified that we can add multiple custom sections in `wasm-tools component embed` that `component new` consumes and seems to merge into a single world.
I started integrating this into `wit-bindgen-go` last night, and quickly learned that `wasm-tools component embed --only-custom` does *not* read WIT from stdin: ```console $ cat wasi-cli.wit | wasm-tools component embed...
I also noticed the output is near identical to wasm-tools component wit --wasm, aside from the version header. What if we removed this new subcommand and relaxed the component type...
Could we add a --world argument?
Makes sense. FWIW, the WIT text passed to this command will already be tree-shaken and contain only a single synthetic world that maps 1:1 to the intersection of an explicit...
Sure. Is there a mechanism to solicit feedback from community on a change like this?
If there is currently no implementation in the wild with (32,64] labels, then changing the flatting rules to an i64 seems possible in the short term?
In Go, the [`io.Reader`](https://go.dev/tour/methods/21) interface reads into a caller-supplied buffer, returning the number of bytes read, or an error. The equivalent here would be: ```wit read: func(dest: buffer) -> result...