rust-analyzer component model · wasmtime

Stream: wasmtime

Topic: rust-analyzer component model

Dave Bakker (badeend) (Oct 14 2023 at 21:12):

Hi! Since https://github.com/bytecodealliance/wasmtime/pull/7029 landed, rust-analyzer just completely bails on anything resource related. At first I thought it was only failing on dynamically generated code from witbindgen, but I just realized it can't even resolve wasmtime::component::Resource, which is just a regular plain code dependency.
image.png

Building via the command line works just fine.
Is this a known issue, or is there something I need to configure locally to make it work?

Start to port Wasmtime to the new wasi-io API with resources. by sunfishcode · Pull Request #7029 · bytecodealliance/wasmtime

This imports the new APIs posted in WebAssembly/wasi-io#46.

Jeff Parsons (Oct 15 2023 at 02:18):

Another "Rust Analyser chokes" issue from before that resources PR: https://github.com/bytecodealliance/cargo-component/issues/139

(No idea if they're actually related; just linking here because the end user facing behaviour is similar.)

Integration with rust-analyzer is broken for bindings · Issue #139 · bytecodealliance/cargo-component

Repro steps cargo component new repro cd repro Run VS Code with rust-analyzer enabled and open src/main.rs. rust-analyzer should trigger a check command that will generate a target/bindings/repro/t...

Dave Bakker (badeend) (Oct 15 2023 at 08:03):

Maybe they're related. That issue mentions restarting rust-analyzer as a workaround, but that doesn't fix it for me.

Last updated: Nov 22 2024 at 17:03 UTC