primoly
primoly
The name generation for Go is quite a bit more involved due to the conversions and collision checks being done in different functions and files and handled differently on a...
Probably irrelevant, but could code alignment play a role? I noticed that both modules compile to basically the same instructions, just assigned different registers. Yet for `func1`, good gets more...
I’ve started some work here: #979
The `preopened_dir` method of `WasiCtxBuilder` was changed in version 20 to return a `Result` and error when a host path can not be opened. Version 19.0.2: https://docs.rs/wasmtime-wasi/19.0.2/wasmtime_wasi/struct.WasiCtxBuilder.html#method.preopened_dir Version 20.0.0: https://docs.rs/wasmtime-wasi/20.0.0/wasmtime_wasi/struct.WasiCtxBuilder.html#method.preopened_dir...
Sorry I just noticed that my previous response is not the real reason for the changed behaviour. That PR only changed the method from taking an open directory to taking...
When I added `serve` I just treated it as a special case of `run`. That’s why it’s in `CargoCommand` instead of `Command`. I didn’t know that `CargoCommand`s don’t get help...
I don’t know the reason for your issue, but if it helps, here are the PRs that renamed/replaced those functions: https://github.com/bytecodealliance/wasmtime/pull/7298/files https://github.com/bytecodealliance/wasmtime/pull/8451/files
I extended the error message in: https://github.com/bytecodealliance/wasm-tools/pull/1654. This does not fully address the issue about the specific cli option, since this is wit-bindgen specific. This would have to go here:...
For what it’s worth, the compilation succeeds but the final output wasm imports the symbols `"env" "memset"` and `"env" "memcpy"`. To avoid this you can use `RUSTFLAGS='-C target-feature=+bulk-memory' cargo component...
The `new` command invokes `cargo add --quiet wit-bindgen-rt --features bitflags`[^1], causing cargo to look for the newest version of that crate (currently 0.29.0), but cargo component itself still uses 0.25.0...