rust-lang / rust-lang/rust-analyzer

No completions after `.` in second argument of `dbg!`

Open
#16,624 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

pub struct Point {
    id1: i32,
    id2: i32,
    id3: i32,
}

impl Point {
    pub fn add_next_state(&mut self) {
        dbg!(self.id1, self.);
    }
}
image

rust-analyzer version:

rust-analyzer version: 0.3.1850-standalone (68c506fd6 2024-02-19)

rustc version: (eg. output of rustc -V)

rustc 1.76.0 (07dca489a 2024-02-04)

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 completion failure using the Rust snippet in the issue, focusing on the second argument of dbg! after self.. Start by tracing how rust-analyzer handles completions inside dbg! macro arguments; done means the Point fields are offered there with rustc 1.76.0 and the reported rust-analyzer version.

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.