rust-lang / rust-lang/rust-analyzer
Add VSCode command to show the `rustc --explain EXXXX` output
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Here is a user story example:
- I use VSCode.
- I have a compilation (analysis) error.
- This error has an explanation code (
For more information about this error, try `rustc --explain EXXXX`.). - I open the command palette and run the command
rust-analyzer: Explain. - It opens a new tab containing the
rustc --explain EXXXXoutput.
There are other considerations to take into account:
- multiple errors
- (rather?) add it in code actions
- how would that reflect in other IDEs/text editors?
If this feature is acceptable (and once the specs would be agreed upon), I could try to contribute by working on it but I must warn that I'm a beginner in Rust, so that would take some time.
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
The issue mentions the rust-analyzer command palette, rustc --explain EXXXX, code actions, multiple errors, and behavior across IDEs and text editors, but no files or tests. First resolve the command versus code-action scope and multi-error behavior; done means an agreed implementation opens the requested explanation output for a diagnostic code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100