-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wit-bindgen bindings for renamed interface #5961
Comments
The cargo expand code has pub mod orange {
...
} pub mod blue {
...
pub type Thing = super::green::Thing;
...
} That reference to |
This updates to the latest wasi-filesystem, wasi-sockets, wasi-io, and wasi-cli wit changes, except for one thing: `filesystem.types` is still named `filesystem.filesystem` to work around bytecodealliance/wasmtime#5961.
This updates to the latest wasi-filesystem, wasi-sockets, wasi-io, and wasi-cli wit changes, except for one thing: `filesystem.types` is still named `filesystem.filesystem` to work around bytecodealliance/wasmtime#5961.
This updates to the latest wasi-filesystem, wasi-sockets, wasi-io, and wasi-cli wit changes, except for two things: - `filesystem.types` is temporarily still named `filesystem.filesystem`, to work around bytecodealliance/wasmtime#5961 - wasi-stderr is temporarily still present, for debugging
This updates to the latest wasi-filesystem, wasi-sockets, wasi-io, and wasi-cli wit changes, except for two things: - `filesystem.types` is temporarily still named `filesystem.filesystem`, to work around bytecodealliance/wasmtime#5961 - wasi-stderr is temporarily still present, for debugging
I think this would be reasonable enough to fix as-is, but I'll also take the opportunity to ask, would you expect something different to be generated here? For example do you think that |
Ah, I think I misspoke above. I'd expect it to have |
This follows the same strategy pioneered by the `wit-bindgen` guest Rust bindgen which keeps track of the latest name of an interface for how to refer to an interface. Closes bytecodealliance#5961
This follows the same strategy pioneered by the `wit-bindgen` guest Rust bindgen which keeps track of the latest name of an interface for how to refer to an interface. Closes bytecodealliance#5961
Oh no worries, just wanted to confirm! I think #5968 should fix this |
This follows the same strategy pioneered by the `wit-bindgen` guest Rust bindgen which keeps track of the latest name of an interface for how to refer to an interface. Closes #5961
This updates to the latest wasi-filesystem, wasi-sockets, wasi-io, and wasi-cli wit changes, except for two things: - `filesystem.types` is temporarily still named `filesystem.filesystem`, to work around bytecodealliance#5961 - wasi-stderr is temporarily still present, for debugging
This updates to the latest wasi-filesystem, wasi-sockets, wasi-io, and wasi-cli wit changes, except for two things: - `filesystem.types` is temporarily still named `filesystem.filesystem`, to work around bytecodealliance#5961 - wasi-stderr is temporarily still present, for debugging
This wit:
with this Rust:
gets this error:
It appears the bindgen-generated bindings for the
neptune
world use the original name of the interfacegreen
rather than the world's nameorange
.For comparison, the wit-bindgen guest bindings do appear to use the
orange
name.The text was updated successfully, but these errors were encountered: