rust-lang / rust-lang/rust-analyzer
Unexpected Activation of rust-analyzer in a Swift Project
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Hello,
I am currently working on a Swift project in Visual Studio Code and have encountered an unexpected behavior with the rust-analyzer extension.
When I press the F5 key to debug my Swift project, the rust-analyzer extension is being triggered. This is unexpected as the rust-analyzer extension should ideally only respond to Rust projects.
Here are the steps to reproduce the issue:
Minimum Reproduction Code: https://github.com/mole828/SwiftLearning/tree/02435b6a83b9c09d936cae252cd5821a74ffcd4c
Clone the Swift project from this repository.
Open the project in Visual Studio Code.
Press F5 to start debugging.
Expected Behavior: The Swift debugger should start.
Actual Behavior: The rust-analyzer extension is triggered.
I have checked my workspace settings and confirmed that they are correctly set up for a Swift project. I have also verified that the launch.json file in the .vscode directory is correctly configured for Swift debugging.
I would appreciate any guidance on how to prevent rust-analyzer from being activated when working on a Swift project.
Thank you for your time and assistance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Swift minimum reproduction, open it in VS Code, and press F5 with the .vscode/launch.json configuration. Trace which rust-analyzer activation or debug behavior occurs instead of the Swift debugger. Done means F5 starts Swift debugging without activating rust-analyzer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, swift, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100