rust-lang / rust-lang/rust-analyzer
Documentation hint discrepency between autocomplete and inner function
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version: 2026-02-09
rustc version: 1.93.1
editor or extension: Helix
relevant settings: n/a
repository link (if public, optional):
cargo initcargo add axum-extra --features json-lines
code snippet to reproduce:
use axum_extra::extract::JsonLines;
fn main() {
JsonLines::ne| //< cursor
}
When autocompleting the function, documentation turns up fine:
However, when I go within the function, no documentation shows up:
This works fine for other functions:
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
Reproduce the issue with cargo init, cargo add axum-extra --features json-lines, and the shown JsonLines::new snippet in Helix. Compare the documentation path used by autocomplete with the path used inside the function, then verify that documentation appears consistently in both contexts without regressing the behavior shown for other functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100