rust-lang / rust-lang/rust-analyzer

"Click for full compiler diagnostic" should include --verbose output.

Open
#17,267 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I just got an error such as:

error: Error message
   --> File.rs:152:17
    |
152 |                 Code Here
    |                 ^^^^^^^^^ I can't code
    |
    = note: the full name for the type has been written to '/a/menacing/af/path/crate_name_because_im_scary-401a5efc9850fa16.long-type-9477686138195945845.txt'
    = note: consider using `--verbose` to print the full type name to the console
    = help: Unhelpful help text.

consider using --verbose to print the full type name to the console

I clicked on 'click for full compiler diagnostic'. That should include such verbose output by default.

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

No source file or test is named in the issue. Start by tracing the implementation of the “click for full compiler diagnostic” action and how compiler diagnostics handle --verbose output; done means the expanded diagnostic includes the full type information that --verbose would print.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.