rust-lang / rust-lang/rust-analyzer

Unresolved Import with "vulkano::instance::InstanceExtensions" when added another extension to Cargo.toml

Open
#11,648 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-support
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

When ever I add an extension that is not vulkano, I get Unresolved import for "vulkano::instance::InstanceExtensions".
Restarting server fixes the issue, untill I change the version of the second extension or add another extension.

rust-analyzer version: 5fae65dd2 2022-03-07 stable

rustc version: 1.59.0 (9d1b2106e 2022-02-23)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with a project that imports vulkano::instance::InstanceExtensions, then add or version-change a non-vulkano extension in Cargo.toml and observe rust-analyzer's diagnostics. Done means the import remains resolved after dependency changes without requiring a server restart.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.